1. Proposed title of this feature request
Full Support for Ansible Vault in Satellite
2. What is the nature and description of the request?
Currently, to use Ansible vault when running a Ansible role from the Satellite, we have to define
the parameter (vault_password_file) in the file (/usr/share/foreman-proxy/.ansible.cfg), however
the changes are not persistence across satellite-installer execution. As the satellite-installer
override the custom parameters with default settings. so we need an option in Satellite GUI
under( Configure > Ansible > something like Credentials page), to add and update vault password.
Also, add the "Vault ID:" option in the same Credentials page, so that Multi-Vault Credentials can be
defined and utilized later during role execution.
Next, need an option in Job template, to pass/assign the vault Credentials, so that specific Credential can
be assigned to the job templates directly.
3. Why does the customer need this? (List the business requirements here)
It gives flexibility to the customers to utilize the product to the fullest.
4. How would the customer like to achieve this? (List the functional requirements here)
Add option in Satellite GUI under( Configure > Ansible > something like Credentials page),
to add and update vault password. Also, add the "Vault ID:" option in the same Credentials page,
so that Multi-Vault Credentials can be utilized during role execution.
Next, need an option in Job template, to pass/assign the vault Credentials, so that specific
Credentials can be assigned to the job templates directly.
5. Is there already an existing RFE upstream or in Red Hat Bugzilla?
Unknown
6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e.satellite 7.0)?
No
7. Is the sales team involved in this request and do they have any additional input?
No
8. List any affected packages or components.
Unknown
After discussing it with our team, we have come to the conclusion that we will not be able to implement the RFE in the foreseeable future.
The current fix[1] we have implemented for ansible.cfg should help using Vault or additional Ansible configurations from the ansible.cfg without it being overridden by the installer.
Additionally, I want to clarify that our project is not meant to replace AAP, and if you want to utilize Vault's full capabilities, we highly recommend using AAP.
Please let me know if you have any questions or concerns.
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1786358
1. Proposed title of this feature request Full Support for Ansible Vault in Satellite 2. What is the nature and description of the request? Currently, to use Ansible vault when running a Ansible role from the Satellite, we have to define the parameter (vault_password_file) in the file (/usr/share/foreman-proxy/.ansible.cfg), however the changes are not persistence across satellite-installer execution. As the satellite-installer override the custom parameters with default settings. so we need an option in Satellite GUI under( Configure > Ansible > something like Credentials page), to add and update vault password. Also, add the "Vault ID:" option in the same Credentials page, so that Multi-Vault Credentials can be defined and utilized later during role execution. Next, need an option in Job template, to pass/assign the vault Credentials, so that specific Credential can be assigned to the job templates directly. 3. Why does the customer need this? (List the business requirements here) It gives flexibility to the customers to utilize the product to the fullest. 4. How would the customer like to achieve this? (List the functional requirements here) Add option in Satellite GUI under( Configure > Ansible > something like Credentials page), to add and update vault password. Also, add the "Vault ID:" option in the same Credentials page, so that Multi-Vault Credentials can be utilized during role execution. Next, need an option in Job template, to pass/assign the vault Credentials, so that specific Credentials can be assigned to the job templates directly. 5. Is there already an existing RFE upstream or in Red Hat Bugzilla? Unknown 6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e.satellite 7.0)? No 7. Is the sales team involved in this request and do they have any additional input? No 8. List any affected packages or components. Unknown