Fixes #36269 - Add check_needs_publish param and logic to publish API #10523
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are the changes introduced in this pull request?
Adds a
check_needs_publish
parameter to the content view publish API (That defaults to false) and determine if publish is needed on CV and don't publish if not needed.Considerations taken when implementing this change?
The needs_publish method is currently implemented for repository change auditing. There's a PR out for factoring in filter + filter rules changes and this PR should work out of the box when merged.
What are the testing steps for this pull request?
hammer content-view publish --id 2 --check-needs-publish true
hammer content-view publish --id 2 --check-needs-publish false
orIn hammer, run
hammer content-view publish --id 2`