toolshed/abra
toolshed/abra
4
2
Fork 18
Code Issues 29 Pull Requests 3 Packages Releases 40 Activity

fix: chaos consistency (deploy/undeploy/rollback/upgrade) #431

Merged
decentral1se merged 1 commits from chaos-consistency into main 2024-07-08 15:24:58 +00:00
Conversation 1 Commits 1 Files Changed 17 +241 -246
decentral1se commented 2024-07-08 12:03:32 +00:00
Owner
Copy Link

Extended fixes beginning @ coop-cloud/organising#559

We now show version and chaosVersion on all deploy/undeploy/rollback/upgrade deployment overviews. This allows operators to see the state of the deployment in all deployment scenarios for chaotic deployments. rollback/upgrade will additionally warn if you're working with a chaos deploy.

Also, --chaos goes away for upgrade/rollback since it just doesn't make sense anymore. You can --chaos on deploy but upgrade/rollback move between known versions. It will soon be possible to specify a chaos commit but via the [<version>] arg in coop-cloud/organising#517 which is a better UI imho.

TODO: write tests.

Extended fixes beginning @ https://git.coopcloud.tech/coop-cloud/organising/issues/559 We now show `version` and `chaosVersion` on all `deploy`/`undeploy`/`rollback`/`upgrade` deployment overviews. This allows operators to see the state of the deployment in all deployment scenarios for chaotic deployments. `rollback`/`upgrade` will additionally warn if you're working with a chaos deploy. Also, `--chaos` goes away for `upgrade`/`rollback` since it just doesn't make sense anymore. You can `--chaos` on deploy but `upgrade`/`rollback` move between known versions. It will soon be possible to specify a chaos commit but via the `[<version>]` arg in https://git.coopcloud.tech/coop-cloud/organising/issues/517 which is a better UI imho. ~~TODO: write tests.~~
🎉 2
decentral1se commented 2024-07-08 12:08:01 +00:00
Author
Owner
Copy Link

Also pending coop-cloud/abra#430 merge & rebase 🤓

~~Also pending https://git.coopcloud.tech/coop-cloud/abra/pulls/430 merge & rebase 🤓~~
decentral1se force-pushed chaos-consistency from 0113b51f4a to 358766630e 2024-07-08 12:51:54 +00:00 Compare
decentral1se force-pushed chaos-consistency from 358766630e to e6d03cb6ac 2024-07-08 15:19:13 +00:00 Compare
decentral1se changed title from wip: fix: chaos consistency (deploy/undeploy/rollback/upgrade) to fix: chaos consistency (deploy/undeploy/rollback/upgrade) 2024-07-08 15:19:26 +00:00
decentral1se force-pushed chaos-consistency from e6d03cb6ac to c33ca1c6bc 2024-07-08 15:24:14 +00:00 Compare
decentral1se merged commit c33ca1c6bc into main 2024-07-08 15:24:58 +00:00
decentral1se deleted branch chaos-consistency 2024-07-08 15:24:58 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
build
go build related issues
ci/cd
Building things with CI/CD
contributing
Dealing with contributing
critical fix
https://docs.coopcloud.tech/federation/resolutions/passed/010/
design
UI/UX
documentation
Documenting all the things
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
meta
relating to the project or repo itself
question
More information is needed
release
Release management
release-candidate
Related to the new release candidate
security
Security related
test
Unit/integration testing
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant abra-bot ammaratef45 Apfelwurm carla cas decentral1se fauno kawaiipunk knoflook lambdabundesverband moritz p4u1 simon trav val yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#431
No description provided.
Delete Branch "chaos-consistency"

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?