Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to migrate a standalone role to a collection #68687

Merged
merged 13 commits into from
May 4, 2020
2 changes: 2 additions & 0 deletions docs/docsite/rst/dev_guide/developing_collections.rst
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,8 @@ Add a 'per plugin type' specific subdirectory here, including ``module_utils`` w

Vars plugins are unsupported in collections. Cache plugins may be used in collections for fact caching, but are not supported for inventory plugins.

.. _collection_module_utils:

module_utils
^^^^^^^^^^^^

Expand Down
2 changes: 2 additions & 0 deletions docs/docsite/rst/dev_guide/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ Find the task that best describes what you want to do:
* I want to :ref:`add a custom plugin or module locally <developing_locally>`.
* I want to figure out if :ref:`developing a module is the right approach <module_dev_should_you>` for my use case.
* I want to :ref:`develop a collection <developing_collections>`.
* I want to :ref:`migrate a role to a collection <migrating_roles>`.

* I've read the info above, and I'm sure I want to develop a module:

Expand Down Expand Up @@ -84,4 +85,5 @@ If you prefer to read the entire guide, here's a list of the pages in order.
developing_module_utilities
developing_collections
collections_galaxy_meta
migrating_roles
overview_architecture