Skip to content

Add a rule around inventory and credential matching #126

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add a rule around inventory and credential matching #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions inventories/README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,21 @@ Ansible provides a lot of https://docs.ansible.com/ansible/latest/plugins/invent
This gives you a complete model of the environment to be automated, with limited effort to maintain it, and no confusion about where to modify it to get the result you need.
====

== An inventory should use a single machine credential
[%collapsible]
====
Explanations::
An inventory should use a single machine (connection) credential. Inventories should not be mixed with hosts that use different credentials.

Rationale::
When running a playbook, only a single machine credential can be specified within AWX/Ansible Automation Platform. Additionally, a single password or SSH key can be provided if operating from the command line.

Examples::
A typical enterprise implementation may have hosts of the same type, for instance, Linux hosts, with different credentials for different environments, such as in a DMZ or a development environment.
Since a job template or CLI playbook run can only use a single machine (connection) credential without introducing substantial complexity, keeping inventories restricted to a single machine credential keeps execution clean.
To workaround this restriction and run a job against all hosts, when using AWX/AAP is to define multiple job templates, one inventory/one machine credential per template, and combine them together in a workflow template.
Similarly, when using the command line, wrapping the commands into a script will allow the user to provide unique credentials for each playbook run.
====

[[differentiate]]
== Differentiate clearly between "As-Is" and "To-Be" information
Expand Down