deploy/upgrade/rollback version arguments can be git hash #517
No Assignees
decentral1se
decentral1se
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#517
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
It would be nice if it's possible to specify a commit hash as
versionparameter of the commandsabra app deploy/upgrade/rollback <app_name> [version], instead of checking out the hash using git and than setting the-Cflag.Oh nice yeh, I guess that we then warn to say "this implies --chaos, doing as instructed"?
I don't imagine we want to have to pass
--chaosexplicitly here as well?I think passing a hash need to be enough to know that it won't deploy a stable release version. But printing an extra warning would be nice as well.
decentral1se referenced this issue2024-03-27 06:24:01 +00:00
decentral1se referenced this issue2024-03-28 13:54:55 +00:00
Now that coop-cloud/abra#431 is in place, I will aim to get this one done next.
I do like the idea of having chaos commits passed as explicitSee coop-cloud/abra#434 for more.[<version>]arguments instead of--chaosonrollback/upgrade. Now that these chaos commits are visibile in the deployment overviews, we have more of a chance of coordinating stable chaos deployments. Coming soon...