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

role argument spec: allow for shared fragments, like with plugins #80657

Open
1 task done
evgeni opened this issue Apr 27, 2023 · 1 comment
Open
1 task done

role argument spec: allow for shared fragments, like with plugins #80657

evgeni opened this issue Apr 27, 2023 · 1 comment
Labels
affects_2.16 feature This issue/PR relates to a feature request. has_pr This issue has an associated PR. P3 Priority 3 - Approved, No Time Limitation

Comments

@evgeni
Copy link
Contributor

evgeni commented Apr 27, 2023

Summary

When writing documentation for plugins, one can use doc_fragments to have a library of common things to document.
For the AnsibleModule.argument_spec people usually use Pythons inheritance (or helpers like url_argument_spec).

When it comes to role argument specs, there is no comparable feature.
When documenting multiple entrypoints in one role, I've seen people using YAML anchors (&/*) to reference the same blocks, but this doesn't work when documenting multiple roles in a collection that share the same "base" parameters (credentials, for example).

It would be cool if we Ansible would have a place (collection_root/meta/role_argument_specs.yml?) that can define a common base that can be referenced later.

Issue Type

Feature Idea

Component Name

role

Additional Information

Code of Conduct

  • I agree to follow the Ansible Code of Conduct
@ansibot
Copy link
Contributor

ansibot commented Apr 27, 2023

Files identified in the description:

  • lib/ansible/playbook/role

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot ansibot added affects_2.16 feature This issue/PR relates to a feature request. needs_triage Needs a first human triage before being processed. labels Apr 27, 2023
@bcoca bcoca added P3 Priority 3 - Approved, No Time Limitation and removed needs_triage Needs a first human triage before being processed. labels Apr 27, 2023
@ansibot ansibot added the has_pr This issue has an associated PR. label Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects_2.16 feature This issue/PR relates to a feature request. has_pr This issue has an associated PR. P3 Priority 3 - Approved, No Time Limitation
Projects
None yet
Development

No branches or pull requests

3 participants