I have made my environment variable changes backwards compatible
Only new env vars were added
I have added a release note entry
Unsure if this is necessary but I'm happy to add notes if we want them 😄
<!--
Thank you for doing recipe maintenance work!
Please mark all checklist items which are relevant for your changes.
Please remove the checklist items which are not relevant for your changes.
Feel free to remove this comment.
-->
* [x] I have deployed and tested my changes
LetsEncrypt challenges passed
* [x] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
No relevant versions to update
* [x] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
Only new env vars were added
* [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
Unsure if this is necessary but I'm happy to add notes if we want them 😄
Although, I've seen people using generated=false but does it work?
I just realise it's `generate=false` and we have no docs for this 😆
https://git.coopcloud.tech/toolshed/abra/src/commit/8dbde3d15869d1eda0bbb71c4e8c43dfe092e5ff/pkg/secret/secret.go#L193
Although, I've seen people using `generated=false` but does it work?
Aha! You're 100% correct. Just tested, generated still threw an error for "secret not generated", generate allowed me to insert the secret without needing one on the server already 😄
I'm 99% sure the generate=false flag should be added to all of the other DNS provider secrets. I'd be happy to open a separate PR for that as well!
Aha! You're 100% correct. Just tested, `generated` still threw an error for "secret not generated", `generate` allowed me to insert the secret without needing one on the server already 😄
I'm 99% sure the `generate=false` flag should be added to all of the other DNS provider secrets. I'd be happy to open a separate PR for that as well!
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.
LetsEncrypt challenges passed
abra.shNo relevant versions to update
Only new env vars were added
Unsure if this is necessary but I'm happy to add notes if we want them 😄
One minor comment but otherwise, LGTM.
I can't test this myself.
Thanks for the PR!
@@ -89,0 +92,4 @@## abra app secret insert {myapp.example.coop} cf_api_key v1 "<CLOUDFLARE_API_KEY>"## cf_api_key is an account API key from Cloudflare that has DNS read + edit permission#COMPOSE_FILE="$COMPOSE_FILE:compose.cloudflare.yml"#SECRET_CLOUDFLARE_EMAIL_VERSION=v1 # generated=falseI just realise it's
generate=falseand we have no docs for this 😆Although, I've seen people using
generated=falsebut does it work?Aha! You're 100% correct. Just tested,
generatedstill threw an error for "secret not generated",generateallowed me to insert the secret without needing one on the server already 😄I'm 99% sure the
generate=falseflag should be added to all of the other DNS provider secrets. I'd be happy to open a separate PR for that as well!Thanks @Zigzagill, a fix PR for the other DNS providers would be excellent 🙏