Global version specification for abra app ... <version>
#541
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#541
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?
For some commands like
abra app deploy/upgrade/rollback
it's now possible to specify a version. But this introduces some inconsistencies as other commands will automatically check out the newest version like #519. Further there is the proposal to specify the version inside the .env file: #533 (comment)I would propose that (almost?) every
abra app
uses this version (either specified directly inside the command or via the env) to checkout the correct version. The version specified in the command should always be preferred over the version specified in the .envFor these commands I think it's critical:
abra app check
abra app command
abra app deploy
abra app upgrade
abra app rollback
abra app new
abra app secrets
Not sure if I forgot some, but I think if we use the version checkout globally for each
abra app
command we should do fine.