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
role argument spec: allow for examples, like with plugins #81734
Comments
Files identified in the description: If these files are incorrect, please update the |
👍 for adding that. Depending on the role a more extensive document would also be useful (something with sections and text between examples), but that's a bit too much IMO - ansible-doc shouldn't become an arbitrary documentation rendering engine. |
@felixfontein a role within a collection could probably do that already with the collection-level docs support we have now. But that doesn't help standalone roles...And I agree- too much for |
Can you point me at the collection level docs you're talking about? |
Notice there is an unfortunate catch-22 - if you want docs like these in docs.ansible.com, you have to write in .rst in a specific directory. If you want docs like these on AutomationHub/GalaxyNG - you have to write in md in a different directory (my guess is it works on galaxyNG but I haven't poked around to verify that). |
Ah right, but those would be really at the collection level, not part of the docs shown for a role in a collection (either via ansible-doc or antsibull-docs). |
correct |
ansible-core: #82671 |
@evgeni Any updates on this? |
Summary
When writing documentation for plugins, one can use
EXAMPLES
to have a (yaml) block with common examples.When it comes to role argument specs, there is no comparable feature (arguably, it's not part of the argument spec for plugins either…).
It would be cool if we Ansible would allow roles to have examples that can be rendered by
ansible-doc
andantsibull-doc
Issue Type
Feature Idea
Component Name
role
Additional Information
Code of Conduct
The text was updated successfully, but these errors were encountered: