Bug 1126819
Summary: | [RFE] Allow users to make a change to a published content view | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | David Davis <daviddavis> |
Component: | Content Views | Assignee: | Katello Bug Bin <katello-bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jameer Pathan <jpathan> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.4 | CC: | bkearney, inecas |
Target Milestone: | Unspecified | Keywords: | FutureFeature |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-13 12:49:15 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Davis
2014-08-05 11:25:33 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. The option 2 seems reasonable to me. Also, it would be nice to not require the version to be promoted to library before going to the next environment: it would be useful for todays world, where there are multiple paths from the library available and I can choose different version to be promote to the next env without need to publish it to library. Another possible solution from Erik mentions being able to promote components of a composite individually. By default, promote should take whatever is in the current environment and push it to the right (eg: test -> prod). However, maybe we need to offer the ability to override that promotion and allow someone to select the underlying versions of the views in the composite view. This is similar to what I think Eric said about the API letting you place an arbitrary version of a CV into any arbitrary environment. By being able to selectively create a combination of arbitrary underlying components in a composite and place it into an environment, you could easily create a "hotfix" view (or update an existing view with the hotfix) and then modify existing environments to use the specific version of the underlying component view. Incremental errata, which were delivered with Satellite 6.1, addresses this bug. Closing this out. |