feat: teach recipe sync to understand new versions #105
No reviewers
Labels
No Label
bug
build
ci/cd
contributing
design
documentation
duplicate
enhancement
help wanted
invalid
meta
question
security
wontfix
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#105
Loading…
Reference in New Issue
No description provided.
Delete Branch "new-recipe-sync"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decisions I made:
we don't need to add a label to every service anymore, we just add it to the
app
service (or whatever the "main" service is of the recipe)we use a simpler label format:
coop-cloud.${STACK_NAME}.version=${RECIPE_TAG}
When I ran this logic on the Gitea recipe, it produced this diff:
Closes coop-cloud/organising#177.
getting rid of the additional labels is a great idea! I'm not getting any errors, this looks ready to be merged
Are we deciding we don't care about upstreams overwriting the same Docker tag with a different image, or is there another way to guard against that instead of tracking the hash in a label? 🤔
Or maybe I'm misunderstanding, this hash business confuses me a bit.
coop-cloud/organising#67