Skip to content

Log cron_jobs configuration instead of raising exception

Gabriel Mazetto requested to merge regression/cron_jobs_validation into master

What does this MR do?

Log cron_jobs configuration errors and remove invalid key <-> values from the configuration hash instead of raising an exception. This has been discussed at #20010 (closed).

Fixes #20010 (closed)

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Original implementation !5318 (merged), introduced a regression with our docker packaging: #20010 (closed).

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Merge request reports