This PR solves #12 by shortening all secret and config names to max 14 characters.
Note that this PR is based on #6, which hasn't been merged yet.
I've briefly tested by deploying the current recipe version and upgrading to this PR:
When deploying the upgrade, all config files are created with the new shortened name. docker config ls still shows the old config files with longer names, they are not automatically cleaned up.
Secrets have to be reinserted with the new, shorter name. This breaks automatic upgrading, but it shouldn't break a running instance because deployment fails if the new shorter secret isn't inserted.
This PR solves #12 by shortening all secret and config names to max 14 characters.
Note that this PR is based on #6, which hasn't been merged yet.
I've briefly tested by deploying the current recipe version and upgrading to this PR:
- When deploying the upgrade, all config files are created with the new shortened name. `docker config ls` still shows the old config files with longer names, they are not automatically cleaned up.
- Secrets have to be reinserted with the new, shorter name. This breaks automatic upgrading, but it shouldn't break a running instance because deployment fails if the new shorter secret isn't inserted.
dannygroenewegen
changed title from Shortened all the secret and config names to max 14 characters to prevent running into Docker's 64 character limit when STACK_NAME is appended to it. to fix: Shorten all secret and config names to max 14 characters2026-03-12 11:42:23 +00:00
decentral1se
requested review from iexos 2026-03-12 12:06:11 +00:00
decentral1se
requested review from p4u1 2026-03-12 12:06:11 +00:00
decentral1se
requested review from moritz 2026-03-12 12:06:18 +00:00
iexos
declined to review 2026-03-12 20:04:56 +00:00
p4u1
changed target branch from seperate-oidc to main2026-03-20 09:10:49 +00:00
p4u1
approved these changes 2026-03-20 09:13:17 +00:00
Thanks a lot! This looks good to me :) I also just merge #6
Could you add a note to the release notes (in release/next) that explains what to do when upgrading?
Thanks a lot! This looks good to me :) I also just merge https://git.coopcloud.tech/coop-cloud/monitoring-ng/pulls/6
Could you add a note to the release notes (in release/next) that explains what to do when upgrading?
Thank you, I really like this PR. I also tried to shorten the secret names of many recipes long ago because we had problems with too long domains.
But changing the secret names is also a huge breaking change, that takes a lot of effort to change all secrets for all deployed apps. I would favor if there is a abra.sh function that can be run with the --local flag, that extracts the actual secrets and automatically inserts them with the new names, before running the update. Just contact if you need help in implementing it.
Thank you, I really like this PR. I also tried to shorten the secret names of many recipes long ago because we had problems with too long domains.
But changing the secret names is also a huge breaking change, that takes a lot of effort to change all secrets for all deployed apps. I would favor if there is a abra.sh function that can be run with the --local flag, that extracts the actual secrets and automatically inserts them with the new names, before running the update. Just contact if you need help in implementing it.
Thank you, I really like this PR. I also tried to shorten the secret names of many recipes long ago because we had problems with too long domains.
But changing the secret names is also a huge breaking change, that takes a lot of effort to change all secrets for all deployed apps. I would favor if there is a abra.sh function that can be run with the --local flag, that extracts the actual secrets and automatically inserts them with the new names, before running the update. Just contact if you need help in implementing it.
I've added migrate_secret_names to abra.sh. It works for me. Can you review if it would fit your needs?
> Thank you, I really like this PR. I also tried to shorten the secret names of many recipes long ago because we had problems with too long domains.
> But changing the secret names is also a huge breaking change, that takes a lot of effort to change all secrets for all deployed apps. I would favor if there is a abra.sh function that can be run with the --local flag, that extracts the actual secrets and automatically inserts them with the new names, before running the update. Just contact if you need help in implementing it.
I've added migrate_secret_names to abra.sh. It works for me. Can you review if it would fit your needs?
@moritz Do you want to review the migrate_secret_names function? Or is it ok for you to merge this so we can move forward? Also happy to prioritise if we want any changes to this function after merging. I'd like to resolve all my chaos deployments. It's a bit awkward to develop chaos on top of chaos.
@moritz Do you want to review the migrate_secret_names function? Or is it ok for you to merge this so we can move forward? Also happy to prioritise if we want any changes to this function after merging. I'd like to resolve all my chaos deployments. It's a bit awkward to develop chaos on top of chaos.
By reading it, it looks all fine to me, but I have not the time to carefully test it at the moment. I will just merge it so the we can move forward. And if something will break we can simply patch it, note it in the release notes and remove the tag from the breaking version.
By reading it, it looks all fine to me, but I have not the time to carefully test it at the moment. I will just merge it so the we can move forward. And if something will break we can simply patch it, note it in the release notes and remove the tag from the breaking version.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This PR solves #12 by shortening all secret and config names to max 14 characters.
Note that this PR is based on #6, which hasn't been merged yet.
I've briefly tested by deploying the current recipe version and upgrading to this PR:
docker config lsstill shows the old config files with longer names, they are not automatically cleaned up.Shortened all the secret and config names to max 14 characters to prevent running into Docker's 64 character limit when STACK_NAME is appended to it.to fix: Shorten all secret and config names to max 14 charactersThanks a lot! This looks good to me :) I also just merge #6
Could you add a note to the release notes (in release/next) that explains what to do when upgrading?
0f4033aa97tocda5c89033Thank you, I really like this PR. I also tried to shorten the secret names of many recipes long ago because we had problems with too long domains.
But changing the secret names is also a huge breaking change, that takes a lot of effort to change all secrets for all deployed apps. I would favor if there is a abra.sh function that can be run with the --local flag, that extracts the actual secrets and automatically inserts them with the new names, before running the update. Just contact if you need help in implementing it.
8cdc3bf744to0ebee51b470ebee51b47to682f30cef1I've added migrate_secret_names to abra.sh. It works for me. Can you review if it would fit your needs?
@moritz Do you want to review the migrate_secret_names function? Or is it ok for you to merge this so we can move forward? Also happy to prioritise if we want any changes to this function after merging. I'd like to resolve all my chaos deployments. It's a bit awkward to develop chaos on top of chaos.
@dannygroenewegen I would say we merge this and make changes later if needed
By reading it, it looks all fine to me, but I have not the time to carefully test it at the moment. I will just merge it so the we can move forward. And if something will break we can simply patch it, note it in the release notes and remove the tag from the breaking version.