Flag to support deploying latest git when versions are already published #178
Labels
No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#178
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
From https://github.com/Autonomic-Cooperative/traefik/pull/1.
I was thinking, well, if you don't publish a version of your app, it is always using the latest HEAD but if you do publish a version, then you're stuck with that and no way to force it to use latest HEAD again.
#176 will help this from the packaging side. But for the hacking it would be good to have a
--chaos
so as to overridea019417fd2/abra (L604-L608)
.I can't really think of a good name for this flag, so I'm just going with
--chaos
because 🤷♀️Looks like we have some saucy undocumented behaviour that when you pass
dev
as the version it does some sort of overriding? I think it does what I am looking for but will add this flag anyway. We can stabilise this later. I want to tweak the deployment overview messages as well.