feat: only_publish_on_change #292
Closed
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.
Description:
This PR allows devs to run the
gdk component publish
command and restrict publishing new versions of the component only when changes are found in the Recipe or Artifact or both.Feature is controlled by the only_on_change option in the publish section of the gdk config. e.g:
"publish": { "bucket": "ggv2artifacts", "region": "eu-west-2", "options": { "only_on_change": ["RECIPE","ARTIFACTS"] } }
This change necessary:
As if you use
gdk component publish
in a pipeline, you do not want to publish if there have been no changes. Currently it always publish and this leads to having a new version of the component for every pipeline run.This change tested:
make tests_unit
and expanded to cover the new options.make tests_integration
and adapted to cover the new options.make tests_unit
Additional information:
Checklist:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.