ea04e0048d
* Allow to deprecate options and aliases by date instead of only by version. * Update display.deprecate(). * Adjust behavior to conform to tested behavior, extend tests, and improve C# style. * Parse date and fail on invalid date. This is mainly to make sure that people start using invalid dates, and we eventually have a mess to clean up. * C# code: improve validation and update/extend tests. * Make sure that deprecate() is not called with both date and version. * Forgot to remove no longer necessary formatting. * Adjust order of warnings in C# code. * Adjust unrelated test. * Fix grammar (and make that test pass). * Don't parse date, and adjust message to be same as in #67684. * Sanity tests: disable date in past test. * Validate-modules: validate ISO 8601 date format. * Validate-modules: switch schema declaration for deprecated_aliases to improve error messages for invalid dates. * Use DateTime instead of string for date deprecation. * Validate that date in deprecated_aliases is actually a DateTime. * Fix tests. * Fix rebasing error. * Adjust error codes for pylint, and add removed_at_date and deprecated_aliases.date checks to validate-modules. * Make deprecation date in the past error codes optional. * Make sure not both version and date are specified for AnsibleModule.deprecate() calls. * Stop using Python 3.7+ API. * Make sure errors are actually reported. Re-add 'ansible-' prefix. * Avoid crashing when 'name' isn't there. * Linting. * Update lib/ansible/module_utils/csharp/Ansible.Basic.cs Co-authored-by: Jordan Borean <jborean93@gmail.com> * Adjust test to latest change. * Prefer date over version if both end up in Display.deprecated(). Co-authored-by: Jordan Borean <jborean93@gmail.com> |
4 years ago | |
|---|---|---|
| .. | ||
| _extensions | 5 years ago | |
| _static | 4 years ago | |
| _themes/sphinx_rtd_theme | 4 years ago | |
| js/ansible | 8 years ago | |
| rst | 4 years ago | |
| .gitignore | 7 years ago | |
| .nojekyll | 8 years ago | |
| Makefile | 5 years ago | |
| Makefile.sphinx | 6 years ago | |
| README.md | 5 years ago | |
| ansible_2_5.inv | 4 years ago | |
| ansible_2_6.inv | 4 years ago | |
| ansible_2_7.inv | 4 years ago | |
| ansible_2_8.inv | 4 years ago | |
| ansible_2_9.inv | 4 years ago | |
| jinja2.inv | 4 years ago | |
| keyword_desc.yml | 4 years ago | |
| modules.js | 8 years ago | |
| python2.inv | 5 years ago | |
| python3.inv | 4 years ago | |
| requirements.txt | 5 years ago | |
| variables.dot | 8 years ago | |
README.md
Ansible documentation
This project hosts the source behind docs.ansible.com.
To create clear, concise, and consistent contributions to Ansible documentation, please refer to the following information.
Contributions
Contributions to the documentation are welcome.
The Ansible community produces guidance on contributions, building documentation, and submitting pull requests, which you can find in Contributing to the Ansible Documentation.
You can also join the Docs Working Group.
Ansible style guide
Ansible documentation is written in ReStructuredText(RST). The Ansible style guide provides linguistic direction and technical guidelines for working with reStructuredText, in addition to other resources.
Tools
The Ansible community uses a range of tools and programs for working with Ansible documentation. Learn more about Other Tools and Programs in the Ansible Community Guide.
GitHub
Ansible documentation is hosted on the Ansible GitHub project. For GitHub workflows and other information, see the GitHub Guides.