Miretpl opened a new pull request, #64339:
URL: https://github.com/apache/airflow/pull/64339

    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   During checking Helm Refurbish, I noticed that some fields are missing. This 
PR adds almost all missing fields in the doc to be rendered.
   
   All modified values:
   1. fullnameOverride
   2. revisionHistoryLimit
   3. nameOverride
   4. useStandardNaming
   5. workers.revisionHistoryLimit
   6. workers.livenessProbe.command
   7. workers.celery.revisionHistoryLimit
   8. workers.celery.livenessProbe.command
   9. scheduler.livenessProbe.command
   10. scheduler.startupProbe.command
   11. scheduler.revisionHistoryLimit
   12. triggerer.livenessProbe.command
   13. triggerer.revisionHistoryLimit
   14. dagProcessor.livenessProbe.command
   15. dagProcessor.revisionHistoryLimit
   16. createUserJob.restartPolicy
   17. migrateDatabaseJob.restartPolicy
   18. apiServer.revisionHistoryLimit
   19. webserver.revisionHistoryLimit
   20. flower.revisionHistoryLimit
   21. statsd.revisionHistoryLimit
   22. pgbouncer.revisionHistoryLimit
   23. cleanup.failedJobsHistoryLimit
   24. databaseCleanup.failedJobsHistoryLimit
   25. databaseCleanup.successfulJobsHistoryLimit
   
   There is a chance that I missed something. In a free moment, I plan to 
prepare a pre-commit hook for checking this file in case of missing fields.
   
   ---
   
   ##### 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]

Reply via email to