🐛 Fix seed dup target labels (#776) #777
Merged
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.
Fixes an issue with duplicate target labels.
Also, add support for a hub build version needed to detect upgrades.
The git tag-hash is written to
/etc/hub-build
. The abbreviatedcommit hash is appended when HEAD is a commit added to the latest label.
Examples:
After seeded, the build is stored in settings:
.hub.db.seed.build
.This is compared with current build to detect when the build has
changed. Seeding is skipped when both the build (version) and the seed
data have not changed.
The go.mod update was to bump go-utils for better logging of objects.
Included here for better logging of the Settings.
Signed-off-by: Jeff Ortel jortel@redhat.com
Signed-off-by: Cherry Picker noreply@github.com