Bug 1311428 - [RFE] expose content view version to puppet modules
Summary: [RFE] expose content view version to puppet modules
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.1.7
Hardware: All
OS: All
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 08:54 UTC by Stefan Meyer
Modified: 2019-08-12 14:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:10:36 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Stefan Meyer 2016-02-24 08:54:01 UTC 
Feature:
Satellite 6 already exposes "lifecycle_environment" and "content_view" as 
parameter for Puppet but not the assigned Content View version.


Reason:
The customer likes to use the Content View Version as information on the 
target systems without having to lookup the system in Satellite 6. 

An example would be an information in /etc/motd.

Result:
Parameter "content_view_version" can be used in Puppet classes and modules
Comment 4 Bryan Kearney 2016-07-26 19:03:46 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 7 Bryan Kearney 2018-09-04 18:58:49 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Comment 8 Bryan Kearney 2018-09-04 19:10:36 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.