Bug 1377893 - [RFE] content view, Check source of puppet module from puppet product
Summary: [RFE] content view, Check source of puppet module from puppet product
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: Unspecified
Hardware: x86_64
OS: Linux
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-20 22:56 UTC by Manikandan Somasundaram
Modified: 2020-12-14 07:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-12 19:29:41 UTC
Target Upstream Version:


Attachments (Terms of Use)

Comment 1 Nagoor Shaik 2017-08-23 11:49:11 UTC
1. Proposed title of this feature request  
   View source of puppet module in the Content View
   
2. What is the nature and description of the request?  
 When there is same puppet module that is present on two different puppet product, content view has created using both of the puppet product, but he wants to check from puppet module us used by content view is from which puppet product.
   

3. Why does the customer need this? (List the business requirements here)  

When there is two puppet product gives the same version of puppet module, they are not able to find the source of the puppet module
  
4. How would the customer like to achieve this? (List the functional requirements here)  

provide an option to check puppet module and its association with puppet product on content view

Comment 2 Bryan Kearney 2017-10-12 19:29:41 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable 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.