Actions
Bug #38460
openComposite content views can update twice due to a single incremental update of a child content view
Description
When a composite content view is both set to auto-publish and contains a content view set to 'Always update to latest version', it will update twice when an incremental update is applied on the child content view and the --propagate-all-composites
flag is set.
- Create and publish a content view with missing errata.
- Add that content view to a composite content view and set the CV to 'Always update to latest version'. Set the CCV to auto-publish.
- Run an incremental update on the CV with the
--propagate-all-composites
flag set:hammer content-view version incremental-update --content-view-version-id <cvv-id> --errata-ids <erratum-id> --propagate-all-composites true
- Look at the new versions of the CCV. There will be a new minor version tracking the incremental update (X.1) and a new major version created in response to the new CV minor version (X+1).
Expected output
There are a few options for fixing this bug. Either
- CCVs should not auto-publish on child CV minor version updates when the
--propagate-all-composites
flag is set, --propagate-all-composites
should not have an effect on CCVs set to auto-publish, or- auto-publishing CCVs should abort new publications when the new version's contents match the old version.
Option #3's approach is probably the cleanest but is also the most expensive. Any approach has lots of edge cases we need to worry about, unfortunately.
Actions