A few comments on this as I'm a bit confused on the usage of secrets/env vars and how they are being threaded through to the app. This seems to go a bit against our well established conventions. I'd invite you to check how other recipes are doing this so we can keep our approaches aligned.
Question: do AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_SUBSCRIPTION_ID and AZURE_RESOURCE_GROUP need to be secrets? They sound more like public env vars? I am not sure then you need to thread them through as secrets?
We normally use lowercase names for secrets. Also, we try to keep them short as possible to avoid secret length limits that are imposed by the runtime. So, e.g. AZURE_CLIENT_SECRET👉client_secret. I would also try to trim down the names below, so e.g. AZURE_SUBSCRIPTION_ID👉sub_id.
We normally don't put the path to the /run/secrets/... in the .env file but instead hardcode it in the compose.yml like so. This could reduce the amount of env vars you need to introduce?
Thanks for the work!
A few comments on this as I'm a bit confused on the usage of secrets/env vars and how they are being threaded through to the app. This seems to go a bit against our well established conventions. I'd invite you to check how other recipes are doing this so we can keep our approaches aligned.
Question: do `AZURE_TENANT_ID`, `AZURE_CLIENT_ID`, `AZURE_SUBSCRIPTION_ID` and `AZURE_RESOURCE_GROUP` need to be secrets? They sound more like public env vars? I am not sure then you need to thread them through as secrets?
We normally use lowercase names for secrets. Also, we try to keep them short as possible to avoid secret length limits that are imposed by the runtime. So, e.g. `AZURE_CLIENT_SECRET` 👉 `client_secret`. I would also try to trim down the names below, so e.g. `AZURE_SUBSCRIPTION_ID` 👉 `sub_id`.
We normally don't put the path to the `/run/secrets/...` in the `.env` file but instead hardcode it in the `compose.yml` like so. This could reduce the amount of env vars you need to introduce? https://git.coopcloud.tech/coop-cloud/peertube/src/commit/2744684292d66053a9681ac57692b9f026863dde/compose.yml#L50
decentral1se
changed title from master to feat: add azure DNS-01 challenge support2025-08-12 05:00:29 +00:00
@decentral1se Thanks for the feedback! I’ve made the updates to match the conventions you mentioned -- the non-sensitive Azure values are now regular env vars, the /run/secrets/... path is set directly in compose.azure.yml, and the secret name is shorter and lowercase. I also added
I went with azure_secret for the client secret so it’s easier to spot when looking through secrets.
@decentral1se Thanks for the feedback! I’ve made the updates to match the conventions you mentioned -- the non-sensitive Azure values are now regular env vars, the `/run/secrets/...` path is set directly in `compose.azure.yml,` and the secret name is shorter and lowercase. I also added
I went with `azure_secret` for the client secret so it’s easier to spot when looking through secrets.
My only comment is that bumping TRAEFIK_YML_VERSION probably shouldn't be necessary, if there's no change to traefik.yml.tmpl. But I don't think it harms anything having it there.
Amazing contribution @ripclap 👏 Thank you!
My only comment is that bumping `TRAEFIK_YML_VERSION` probably shouldn't be necessary, if there's no change to `traefik.yml.tmpl`. But I don't think it harms anything having it there.
Oh sorry @ammaratef45, forgot to hold off on clicking the button as you mentioned you would sort it in #56 (comment). Thanks again @ripclap👏 If you're interested in getting more involved and holding the commit bit (read/write on coop-cloud repos), come find us in the matrix chat!
Oh sorry @ammaratef45, forgot to hold off on clicking the button as you mentioned you would sort it in https://git.coopcloud.tech/coop-cloud/traefik/pulls/56#issuecomment-25590. Thanks again @ripclap 👏 If you're interested in getting more involved and holding the commit bit (read/write on coop-cloud repos), come find us in the matrix chat!
Oh sorry @ammaratef45, forgot to hold off on clicking the button as you mentioned you would sort it in #56 (comment). Thanks again @ripclap👏 If you're interested in getting more involved and holding the commit bit (read/write on coop-cloud repos), come find us in the matrix chat!
Just joined!
> Oh sorry @ammaratef45, forgot to hold off on clicking the button as you mentioned you would sort it in https://git.coopcloud.tech/coop-cloud/traefik/pulls/56#issuecomment-25590. Thanks again @ripclap 👏 If you're interested in getting more involved and holding the commit bit (read/write on coop-cloud repos), come find us in the matrix chat!
Just joined!
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.
Added Azure DNS-01 Challenge support
Nice work! I'll test it locally and merge/release once I confirm it all works <3
e095fa2e88to2db1a03d94Thanks for the work!
A few comments on this as I'm a bit confused on the usage of secrets/env vars and how they are being threaded through to the app. This seems to go a bit against our well established conventions. I'd invite you to check how other recipes are doing this so we can keep our approaches aligned.
Question: do
AZURE_TENANT_ID,AZURE_CLIENT_ID,AZURE_SUBSCRIPTION_IDandAZURE_RESOURCE_GROUPneed to be secrets? They sound more like public env vars? I am not sure then you need to thread them through as secrets?We normally use lowercase names for secrets. Also, we try to keep them short as possible to avoid secret length limits that are imposed by the runtime. So, e.g.
AZURE_CLIENT_SECRET👉client_secret. I would also try to trim down the names below, so e.g.AZURE_SUBSCRIPTION_ID👉sub_id.We normally don't put the path to the
/run/secrets/...in the.envfile but instead hardcode it in thecompose.ymllike so. This could reduce the amount of env vars you need to introduce?masterto feat: add azure DNS-01 challenge support@decentral1se Thanks for the feedback! I’ve made the updates to match the conventions you mentioned -- the non-sensitive Azure values are now regular env vars, the
/run/secrets/...path is set directly incompose.azure.yml,and the secret name is shorter and lowercase. I also addedI went with
azure_secretfor the client secret so it’s easier to spot when looking through secrets.Amazing contribution @ripclap 👏 Thank you!
My only comment is that bumping
TRAEFIK_YML_VERSIONprobably shouldn't be necessary, if there's no change totraefik.yml.tmpl. But I don't think it harms anything having it there.Amazing, thanks @ripclap! Pending 3wcs point on #56 (comment) this LGTM!
Oh sorry @ammaratef45, forgot to hold off on clicking the button as you mentioned you would sort it in #56 (comment). Thanks again @ripclap 👏 If you're interested in getting more involved and holding the commit bit (read/write on coop-cloud repos), come find us in the matrix chat!
Just joined!