abra app upgrade (and friends) warn about missing secret versions for irrelevant secrets #671

Closed
opened 2025-09-17 15:04:08 +00:00 by 3wordchant · 2 comments
Owner
abra app upgrade tv.lumbung.space
...
WARN: (SECRET_PEERTUBE_SECRET_VERSION not generated)

Even if the .env doesn't reference compose.peertube-secret.yml

``` abra app upgrade tv.lumbung.space ... WARN: (SECRET_PEERTUBE_SECRET_VERSION not generated) ``` Even if the `.env` doesn't reference `compose.peertube-secret.yml`
3wordchant added the
bug
label 2025-09-17 15:04:08 +00:00
Author
Owner

CC @rscmbbng

CC @rscmbbng
decentral1se added this to the Abra v0.12 project 2025-09-18 07:57:13 +00:00
decentral1se moved this to Prioritised in Abra v0.12 on 2025-09-28 22:56:59 +00:00
decentral1se started working 2025-09-29 06:31:53 +00:00
decentral1se moved this to In Progress in Abra v0.12 on 2025-09-29 06:32:02 +00:00
Owner

Hey @3wordchant @rscmbbng

I couldn't reproduce this with the WARN: (SECRET_PEERTUBE_SECRET_VERSION not generated) message 🤔 Idk if that was just some copy/paste issue or some difference between abra versions. I can't find any string that would look like that but maybe my grepping powers are failing me now. What I did see is: WARN SECRET_PEERTUBE_SECRET_VERSION missing from foo.com.env

However, it would seem that you didn't comment out these env vars by default in the .env.sample?

.env.sample Lines 17 to 18 in c1dcf6d507
COMPOSE_FILE="$COMPOSE_FILE:compose.peertube-secret.yml"
SECRET_PEERTUBE_SECRET_VERSION=v1

abra is basically doing a compare of the .env.sample and the current deployment .env at this point in the runtime logic. If it seems uncommented out env vars, then it will show a warning if they are not present in the deployment .env. I am gonna open a ticket on the Peertube recipe about what to do about this.

If there's more to this issue, please re-open it!

Hey @3wordchant @rscmbbng I couldn't reproduce this with the `WARN: (SECRET_PEERTUBE_SECRET_VERSION not generated)` message 🤔 Idk if that was just some copy/paste issue or some difference between `abra` versions. I can't find any string that would look like that but maybe my grepping powers are failing me now. What I did see is: `WARN SECRET_PEERTUBE_SECRET_VERSION missing from foo.com.env` However, it would seem that you didn't comment out these env vars by default in the `.env.sample`? https://git.coopcloud.tech/coop-cloud/peertube/src/commit/c1dcf6d5077fb5e09049fa40352e2381611747c7/.env.sample#L17-L18 `abra` is basically doing a compare of the `.env.sample` and the current deployment `.env` at this point in the runtime logic. If it seems uncommented out env vars, then it will show a warning if they are not present in the deployment `.env`. I am gonna open a ticket on the Peertube recipe about what to do about this. If there's more to this issue, please re-open it!
decentral1se worked for 21 minutes 2025-09-29 06:53:07 +00:00
decentral1se moved this to Done in Abra v0.12 on 2025-09-29 06:57:35 +00:00
Sign in to join this conversation.
2 Participants
Notifications
Total Time Spent: 21 minutes
decentral1se
21 minutes
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#671
No description provided.