Composite views allow promotions beyond what they should
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1174237
If you have a content view (lets call it CV-A) that is in the Library environment. Now if I create a composite content view (lets call it CCV-A) and I add CV-A to this:
CCV-A |-- CV-A
I should NOT be able to promote CCV-A beyond the Library environment as the content views it is a member of are not at that level. I.e. I should not be able to promote CCV-A beyond the lowest environment of the content views.
fixes #13057 - composite views: add option to restrict publish and promotion
This commit adds an optional 'setting' to enable a user to
restrict/deny composite content view publishing and promotion,
if any of the composite's component content view versions are
not currently in the target environment.
If a component view version 3.0 (e.g. CVV-A-3.0) is associated
with the composite view:
- the composite view may not be published, if CVV-A-3.0 is not in Library
- the composite view version may not be promoted, if the target environment
(e.g. Dev) does not contain CVV-A-3.0.