deploy/upgrade/rollback version arguments (which autocomplete) #204

New Issue

decentral1se · 2021-10-14T10:28:09Z

decentral1se commented

2021-10-14 10:28:09 +00:00

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.

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.

decentral1se added this to the Versioning and deploy stability milestone 2021-10-14 10:28:11 +00:00

decentral1se added the

enhancement

abra

labels 2021-10-14 10:28:11 +00:00

decentral1se added this to the Beta release (software) project 2021-10-14 10:28:26 +00:00

decentral1se self-assigned this 2021-10-14 10:29:53 +00:00

decentral1se removed their assignment 2021-10-14 18:34:09 +00:00

decentral1se removed this from the Beta release (software) project 2021-10-14 18:34:19 +00:00

decentral1se added this to the Beta release (software) project 2022-05-16 13:31:57 +00:00

decentral1se added

bug

and removed

enhancement

labels 2022-05-16 14:34:39 +00:00

decentral1se modified the project from Beta release (software) to (deleted)

2022-06-17 09:40:35 +00:00

decentral1se added

enhancement

and removed

bug

labels 2022-10-22 12:11:41 +00:00

decentral1se referenced this issue

2023-04-10 11:00:36 +00:00

Upgrade env config only #440

decentral1se commented

2023-04-12 09:32:34 +00:00

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.

👍 1

decentral1se referenced this issue

2023-04-12 09:39:16 +00:00

Upgrade env config only #440

decentral1se changed title from ~~deploy/upgrade/downgrade should accept version arguments (which autocomplete)~~ to deploy/upgrade/rollback version arguments (which autocomplete)

2023-04-12 09:40:30 +00:00

decentral1se referenced this issue

2023-09-21 09:48:14 +00:00

Only the last release note is shown #441

decentral1se added a new dependency 2023-09-21 09:52:03 +00:00

#441 Only the last release note is shown

decentral1se self-assigned this 2023-09-22 09:31:18 +00:00

decentral1se referenced this issue from coop-cloud/abra

2023-09-22 10:34:48 +00:00

Version arguments, local tag lookups & release notes fix #355

decentral1se commented

2023-09-22 10:44:21 +00:00

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...

OK, working on this: https://git.coopcloud.tech/coop-cloud/abra/pulls/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...

decentral1se referenced this issue from a commit

2023-09-23 07:18:47 +00:00

feat: version arguments, local tag lookups & release notes

decentral1se closed this issue

2023-09-23 07:22:09 +00:00

Sign in to join this conversation.