deploy/upgrade/rollback version arguments (which autocomplete) #204
No Assignees
decentral1se
decentral1se
Notifications
Due Date
No due date set.
Blocks
#441 Only the last release note is shown
toolshed/organising
Reference: toolshed/organising#204
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?
There is only an interactive version chooser now but you should be able to jump around to whatever version you want as long as it is in the right direction. We could add a
[<version>]to all commands and make sure those auto-complete from the catalogue versions.Maybe we could extend this to accept a commit hash argument too? Sometimes you wanna do a specific chaos deployment too and I'm pretty sure we could chaotically auto-complete on commit hashs + short log output. Ofc recipe hackers can just check out their own shit too but maybe this is sometimes handy. Idk.
deploy/upgrade/downgrade should accept version arguments (which autocomplete)to deploy/upgrade/rollback version arguments (which autocomplete)OK, working on this: coop-cloud/abra#355 I won't implement autocompletion of versions or passing hash arguments cus the code is already difficult to navigate. rn you can do
abra app deploy/upgrade <version>and that's pretty cool already! PR is WIP... more soon...