rjgoyln opened a new pull request, #64164: URL: https://github.com/apache/airflow/pull/64164
### Description This PR adds the ability to define ttlSecondsAfterFinished for the databaseCleanup CronJob in the Airflow Helm Chart. ### Changes: * Modified templates/database-cleanup/database-cleanup-cronjob.yaml to include the ttlSecondsAfterFinished field in the Job spec. * Added ttlSecondsAfterFinished with a default value of null (~) to values.yaml. * Updated values.schema.json to include the new property for validation. * Added a unit test in tests/helm_tests/airflow_aux/test_database_cleanup.py to ensure the parameter is correctly rendered. * closes: #64152 ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [ ] Yes (please specify the tool below) <!-- Generated-by: [Tool Name] following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --> --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
