toolshed/organising
toolshed/organising
8
1
Fork 0
Code Issues 120 Pull Requests Releases Activity

Chaos deploy written to .env overrides stable deploy #662

New Issue
Closed
opened 2024-12-30 17:39:17 +00:00 by decentral1se · 0 comments
decentral1se commented 2024-12-30 17:39:17 +00:00
Owner
Copy Link

It's a brave new world.

  • hack on recipe
  • abra app deploy foo.com -C
  • <hash>+U gets written to foo.com.env
  • wipe changes on recipe
  • abra app deploy foo.com
  • run into #651 (ignore for now, manually remove +U from the foo.com.env 😅)
  • see the deploy overview

Firstly, it shouldn't deploy without --force/--chaos 🙈

Secondly, the deploy overview shows:

  • "current chaos": <hash>+U (correct)
  • "new chaos": <hash> (wrong)

In this case, I'm deploying the latest release tag (automatically chosen when running app app deploy). However, because <hash> is in the foo.com.env, the logic overrides and assumes a chaos deploy.

In this case, we should not override unless we pass --chaos again.

It's a brave new world. * hack on recipe * `abra app deploy foo.com -C` * `<hash>+U` gets written to `foo.com.env` * wipe changes on recipe * `abra app deploy foo.com` * ~~run into https://git.coopcloud.tech/toolshed/organising/issues/651 (ignore for now, manually remove `+U` from the `foo.com.env` 😅)~~ * see the deploy overview Firstly, it shouldn't deploy without `--force/--chaos` 🙈 Secondly, the deploy overview shows: * "current chaos": `<hash>+U` (correct) * "new chaos": `<hash>` (wrong) In this case, I'm deploying the latest release tag (automatically chosen when running `app app deploy`). However, because `<hash>` is in the `foo.com.env`, the logic overrides and assumes a chaos deploy. In this case, we should not override unless we pass `--chaos` again.
decentral1se added the
bug
abra
 labels 2024-12-30 17:39:17 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
abra
Everything to do with abra
abra-gandi
Abra Gandi plugin
awaiting-feedback
Ping/pong on comms
backups
bug
Something is not working
build
Go build related issues
ci/cd
Getting the robots into the mix
community organising
Opening this thing up
contributing
Contributors stuff
coopcloud.tech
Our main website
democracy
Democratic decision making
design
Design thinking required
documentation
Let's write things together
duplicate
This issue or pull request already exists
enhancement
New feature
finance
Money things
funding
Anything related to grant funding
good first issue
Easy start with development
help wanted
Need some help
installer
Installation related issues
kadabra
performance
Performance related
proposal
Large change which requires feedback & decisin making
question
More information is needed
recipes.coopcloud.tech
Our recipes catalogue
security
Securing our shit
test
Unit or integration test suite
wontfix
This won't be fixed
No Label
abra
bug
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/organising#662
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?