Reconsidering deploy --update
/ rollback
#137
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
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#137
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?
Suggestion:
abra app <app> deploy
just handles initial deploys, and re-deploys with--force
abra app <app> upgrade
just handles upgrades -- latest version by default, or specified new versionabra app <app> rollback
(ordowngrade
?) just handles downgrades -- latest-but-one version by default, or specified older version.So the three subcommands are very similar, except
deploy
won't allow a version change,upgrade
only allows version upgrades (and defaults to latest available),rollback
only allows downgrades (and defaults to latest-but-one).But wide open to other ideas.
Great! One minor comment:
If that jumps a major version, it would probably be bad. So let's get a review/prompt in there for sure to make sure people know what is going on before making the deployment.
Will be discussed over in coop-cloud/go-abra#15.