Bug 1792341 - RFE: add capability to apply/run Ansible roles at the life cycle environment level [NEEDINFO]
Summary: RFE: add capability to apply/run Ansible roles at the life cycle environment ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-17 14:32 UTC by Daniel Leroux
Modified: 2023-09-07 21:30 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-20 14:57:18 UTC
Target Upstream Version:
Embargoed:
bkearney: needinfo? (dleroux)
mhulan: needinfo? (dleroux)


Attachments (Terms of Use)

Description Daniel Leroux 2020-01-17 14:32:52 UTC
Description of problem:

Currently, ansible variables can be defined at three different levels only:
- global
- Host Group
- Host parameters

this RFE is about adding 'lifecycle environments' to that list 


Version-Release number of selected component (if applicable):

6.X

How reproducible:

N/A: this is an RFE 

Additional info:

This is requested for a customer who used to test their puppet modules in different lifecycle environments. After transforming the puppet modules into Ansible roles,  defining variables (globally, host group or host parameters) is a drastic change impacting the current system management method in place.

Comment 10 Bryan Kearney 2020-03-20 14:57:18 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.


Note You need to log in before you can comment on or make changes to this bug.