ansible

Commit Graph

Author	SHA1	Message	Date
Felix Fontein	841bdb74eb	Replace antsibull with antsibull-docs (#77504 )	3 years ago
Felix Fontein	7075fa36a1	Bump requirements for antsibull to 0.42.0 (which depends on antsibull-changelog >= 0.14.0). (#77362 )	3 years ago
Felix Fontein	bc1e29d722	Bump antsibull version from 0.40.1 to 0.41.0 and ansible sphinx theme version to fix HTML generation in return value tables (#76759 ) * Use Jinja2 comment instead of HTML comment to avoid W3C validator warning (-- inside comment). (For those interested in the history of this: http://www.howtocreate.co.uk/SGMLComments.html#doubledash)	3 years ago
Felix Fontein	c53e6d94e9	Use antsibull 0.40.1 for docsite build (#76675 )	3 years ago
Matt Clay	bb63c97c16	ansible-test - Update import test and sanity requirements. (#76308 ) * Add script to freeze sanity requirements. * Declare sanity test requirements and freeze * Use pinned requirements for import.plugin test. * Expand scope of import test for ansible-core. * Add ignores for galaxy import errors. * Update test-constraints sanity test.	3 years ago
Matt Clay	4ea8d9a782	ansible-test - split controller/target testing (#75605 )	3 years ago
Sviatoslav Sydorenko	346c7a765d	Use `sphinx_ansible_theme` Sphinx theme in docs (#74318 )	3 years ago
Matt Clay	f533d46572	Fix ansible-test constraints issues. (#73578 ) * Silence Python 3.5 EOL notice in pip. * Skip import test on compat/selinux.py utils. * Improve Python version skip warning. * Use Python 3.6 as minimum Python for sanity tests. * Improve min Python handling for code-smell tests. * Overhaul test-constraints sanity test. * Merge sanity test constraints with requirements. * Remove legacy content specific constraints. * Add changelog fragment.	4 years ago
Sviatoslav Sydorenko	595413d113	Replace the inhouse collection dependency resolver with `resolvelib` PR #72591 This change: * Adds an artifacts manager that abstracts away extracting the metadata from artifacts, downloading and caching them in a temporary location. * Adds `resolvelib` to direct ansible-core dependencies[0]. * Implements a `resolvelib`-based dependency resolver for `collection` subcommands that replaces the legacy in-house code. This is a dependency resolution library that pip 20.3+ uses by default. It's now integrated for use for the collection dependency resolution in ansible-galaxy CLI. * Refactors of the `ansible-galaxy collection` CLI. In particular, it: - reimplements most of the `download`, `install`, `list` and `verify` subcommands from scratch; - reuses helper bits previously moved out into external modules; - replaces the old in-house resolver with a more clear implementation based on the resolvelib library[0][1][2]. * Adds a multi Galaxy API proxy layer that abstracts accessing the version and dependencies via API or local artifacts manager. * Makes `GalaxyAPI` instances sortable. * Adds string representation methods to `GalaxyAPI`. * Adds dev representation to `GalaxyAPI`. * Removes unnecessary integration and unit tests. * Aligns the tests with the new expectations. * Adds more tests, integration ones in particular. [0]: https://pypi.org/p/resolvelib [1]: https://github.com/sarugaku/resolvelib [2]: https://pradyunsg.me/blog/2020/03/27/pip-resolver-testing Co-Authored-By: Jordan Borean <jborean93@gmail.com> Co-Authored-By: Matt Clay <matt@mystile.com> Co-Authored-By: Sam Doran <sdoran@redhat.com> Co-Authored-By: Sloane Hertel <shertel@redhat.com> Co-Authored-By: Sviatoslav Sydorenko <webknjaz@redhat.com> Signed-Off-By: Sviatoslav Sydorenko <webknjaz@redhat.com>	4 years ago
Toshio Kuratomi	9dda393d70	Collections docs generation (#59761 ) * Build documentation for Ansible-2.10 (formerly known as ACD). Builds plugin docs from collections whose source is on galaxy The new command downloads collections from galaxy, then finds the plugins inside of them to get the documentation for those plugins. * Update the python syntax checks * docs builds can now require python 3.6+. * Move plugin formatter code out to an external tool, antsibull-docs. Collection owners want to be able to extract docs for their own websites as well. * The jinja2 filters, tests, and other support code have moved to antsibull * Remove document_plugins as that has now been integrated into antsibull-docs * Cleanup and bugfix to other build script code: * The Commands class needed to have its metaclass set for abstractmethod to work correctly * Fix lint issues in some command plugins * Add the docs/docsite/rst/collections to .gitignore as everything in that directory will be generated so we don't want any of it saved in the git repository * gitignore the build dir and remove edit docs link on module pages * Add docs/rst/collections as a directory to remove on make clean * Split the collections docs from the main docs * remove version and edit on github * remove version banner for just collections * clarify examples need collection keyword defined * Remove references to plugin documentation locations that no longer exist. * Perhaps the pages in plugins/.rst should be deprecated altogether and their content moved? If not, perhaps we want to rephrase and link into the collection documentation? * Or perhaps we want to link to the plugins which are present in collections/ansible/builtin? * Remove PYTHONPATH from the build-ansible calls One of the design goals of the build-ansible.py script was for it to automatically set its library path to include the checkout of ansible and the library of code to implement itself. Because it automatically includes the checkout of ansible, we don't need to set PYTHONPATH in the Makefile any longer. * Create a command to only build ansible-base plugin docs * When building docs for devel, only build the ansible-base docs for now. This is because antsibull needs support for building a "devel tree" of docs. This can be changed once that is implemented * When building docs for the sanity tests, only build the ansible-base plugin docs for now. Those are the docs which are in this repo so that seems appropriate for now.	4 years ago
Matt Clay	7bff3d312f	Split out and install sanity test requirements. (#69971 ) * Split out sanity test requirements. * Run each --venv test separately. This provides verification that the requirements for each test are properly specified. * Use a separate requirements file per sanity test. * Skip setuptools/cryptography setup for sanity. * Eliminate pyyaml missing warning. * Eliminate more pip noise. * Fix conflicting generate_pip_install commands. * Add changelog fragment.	4 years ago

11 Commits (f5cac6bc5d6dcf8a6acc1b32e8b77452b7be646f)