toolshed/organising
7
1
Fork 0
Code Issues 100 Pull Requests Releases Activity

Upgrade env config only #440

New Issue
Closed
opened 2023-04-06 15:49:18 +00:00 by moritz · 7 comments
moritz commented 2023-04-06 15:49:18 +00:00
Member
Copy Link

It would be nice to have a way to change the .env config without executing abra app undeploy and abra app deploy again, which can lead to hidden upgrades: coop-cloud/organising#434
Something like abra app upgrade --env / -E

The actual way is to run abra app ls -S to find out the current version. Checkout the recipe repo into this version and then run abra app upgrade -C. This could be combined into one command.

It would be nice to have a way to change the .env config without executing `abra app undeploy` and `abra app deploy` again, which can lead to hidden upgrades: https://git.coopcloud.tech/coop-cloud/organising/issues/434 Something like `abra app upgrade --env / -E` The actual way is to run `abra app ls -S` to find out the current version. Checkout the recipe repo into this version and then run `abra app upgrade -C`. This could be combined into one command.
moritz added the
enhancement
 label 2023-04-06 15:49:18 +00:00
decentral1se commented 2023-04-10 11:00:36 +00:00
Owner
Copy Link

@moritz I'm not sure I understand this one. What in the .env do you want to update? You are mentioning versions but no versioning information is currently stored in the .env files?

For the version deployment issues, yeh, that is a pain currently. You could upgrade/rollback currently but then there is no auto-complete on the versions. I think coop-cloud/organising#204 would solve this?

You can also use abra app version. I just checked that and it says in the --help:

Show all information about versioning related to a deployed app. This includes
the individual image names, tags and digests. But also the Co-op Cloud recipe
version.

But actually, I don't think that's correct. I'll open a separate ticket.

@moritz I'm not sure I understand this one. What in the `.env` do you want to update? You are mentioning versions but no versioning information is currently stored in the `.env` files? For the version deployment issues, yeh, that is a pain currently. You could `upgrade`/`rollback` currently but then there is no auto-complete on the versions. I think https://git.coopcloud.tech/coop-cloud/organising/issues/204 would solve this? You can also use `abra app version`. I just checked that and it says in the `--help`: > Show all information about versioning related to a deployed app. This includes the individual image names, tags and digests. But also the Co-op Cloud recipe version. But actually, I don't think that's correct. I'll open a separate ticket.
moritz commented 2023-04-12 07:35:22 +00:00
Author
Member
Copy Link

@moritz I'm not sure I understand this one. What in the .env do you want to update? You are mentioning versions but no versioning information is currently stored in the .env files?

abra app upgrade only works if there is a new version, but often I want to update only the .env configuration without changing the deployed version and without undeploying everything. Therefore I thought something like abra app upgrade --env / -E would be nice. Or maybe abra app env-update to avoid any confusion with version upgrades.

The actual way is to run abra app ls -S to find out the current version. Checkout the recipe repo into this version and then run abra app upgrade -C. This could be combined into one command.

Using this workaround I can update env variables and only the container that are affected by the changes are restarted.

> @moritz I'm not sure I understand this one. What in the `.env` do you want to update? You are mentioning versions but no versioning information is currently stored in the `.env` files? `abra app upgrade` only works if there is a new version, but often I want to update only the .env configuration without changing the deployed version and without undeploying everything. Therefore I thought something like `abra app upgrade --env / -E` would be nice. Or maybe `abra app env-update` to avoid any confusion with version upgrades. > The actual way is to run `abra app ls -S` to find out the current version. Checkout the recipe repo into this version and then run `abra app upgrade -C`. This could be combined into one command. Using this workaround I can update env variables and only the container that are affected by the changes are restarted.
decentral1se commented 2023-04-12 09:39:16 +00:00
Owner
Copy Link

abra app upgrade only works if there is a new version, but often I want to update only the .env configuration without changing the deployed version and without undeploying everything ... I can update env variables and only the container that are affected by the changes are restarted.

I was going to say, "isn't this upgrade --force / deploy --force"? But then I ran into coop-cloud/organising#444 🙃

I thought deploy --force does this?

You still have to manually manage the versions carefully because coop-cloud/organising#434 / coop-cloud/organising#204 are not solved. We should get around to this soon.

> abra app upgrade only works if there is a new version, but often I want to update only the .env configuration without changing the deployed version and without undeploying everything ... I can update env variables and only the container that are affected by the changes are restarted. I was going to say, "isn't this `upgrade --force` / `deploy --force`"? But then I ran into https://git.coopcloud.tech/coop-cloud/organising/issues/444 🙃 I thought `deploy --force` does this? You still have to manually manage the versions carefully because https://git.coopcloud.tech/coop-cloud/organising/issues/434 / https://git.coopcloud.tech/coop-cloud/organising/issues/204 are not solved. We should get around to this soon.
moritz commented 2023-04-12 13:54:00 +00:00
Author
Member
Copy Link

Nice upgrade --force / deploy --force is almost doing what I want, despite the version issue. Is there a difference between these two commands? Also between upgrade -C / deploy -C ? This is a bit confusing.

Nice `upgrade --force / deploy --force` is almost doing what I want, despite the version issue. Is there a difference between these two commands? Also between `upgrade -C / deploy -C` ? This is a bit confusing.
decentral1se commented 2023-04-12 18:00:52 +00:00
Owner
Copy Link

Is there a difference between these two commands? Also between upgrade -C / deploy -C ? This is a bit confusing.

Yeh, this was some early UI/UX that nobody really questioned until now 😆 I'm pretty sure both of those are exactly the same but I haven't checked the code again. Maybe we should make change here... you can't force the upgrade? 🤷‍♀️

> Is there a difference between these two commands? Also between upgrade -C / deploy -C ? This is a bit confusing. Yeh, this was some early UI/UX that nobody really questioned until now 😆 I'm pretty sure both of those are exactly the same but I haven't checked the code again. Maybe we should make change here... you can't force the upgrade? 🤷‍♀️
decentral1se added this to the (deleted) project 2023-06-08 09:27:39 +00:00
decentral1se commented 2023-10-05 12:53:06 +00:00
Owner
Copy Link

OK, let's converge on #434 following coop-cloud/organising#434 (comment). Gathering energy for a speedrun...

OK, let's converge on #434 following https://git.coopcloud.tech/coop-cloud/organising/issues/434#issuecomment-18089. Gathering energy for a speedrun...
decentral1se commented 2023-10-06 17:31:34 +00:00
Owner
Copy Link

Also, you can now do abra app version <domain> and get the version and then run: abra app deploy <domain> <version> -fwhich is more repeatable. Hopefully with pinned & synced versions, this will more automated in the future.

Also, you can now do `abra app version <domain>` and get the version and then run: `abra app deploy <domain> <version> -f`which is more repeatable. Hopefully with pinned & synced versions, this will more automated in the future.
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
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm carla cas coopcloud cyrnel decentral1se fauno iexos jade jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie moritz notplants p4u1 pharaohgraphy renovate-bot ripclap simon sixsmith trav val yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/organising#440
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?