When working with puppet modules in content views, show the origin repo (or get rid of repos)
The new content view workflow is much improved, however there is a slight problem in that the origin repository for puppet modules is not indicated.
If we are going to offer the ability to create multiple products/repos for puppet modules, then we should provide some mechanism to find them via that categorization in the view area.
For example, add a (Sortable/Filterable) column to the "add module" page that displays the origin product/repo of the module.
Also, add the same column to the module list page for the view.
The alternative is to entirely re-vamp the way puppet modules are treated from a product/repo perspective. I would think adding some columns to the pages might be easier.
#4 Updated by Eric Helms about 5 years ago
- Subject changed from [RFE] When working with puppet modules in content views, show the origin repo (or get rid of repos) to When working with puppet modules in content views, show the origin repo (or get rid of repos)
- Legacy Backlogs Release (now unused) set to 14
#7 Updated by John Mitsch about 2 months ago
- Target version deleted (
- Status changed from New to Rejected
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.