Deployment fails due to missing secret #2

Closed
opened 2022-05-19 21:25:48 +00:00 by aadil · 3 comments
Owner
abra app deploy pocket.aadils.computer
WARN[0007] no versions detected, using latest commit    
WARN[0007] no published release discovered for wallabag 
+-----------------+----------+-------------+------------------------+----------+
|     SERVER      |  RECIPE  |   CONFIG    |         DOMAIN         | VERSION  |
+-----------------+----------+-------------+------------------------+----------+
| aadils.computer | wallabag | compose.yml | pocket.aadils.computer | 3da361aa |
+-----------------+----------+-------------+------------------------+----------+
? continue with deployment? Yes
INFO[0010] Creating network pocket_aadils_computer_internal 
FATA[0010] service app: secret not found: pocket_aadils_computer_db_password_v1

may be related to #1?

```sh abra app deploy pocket.aadils.computer WARN[0007] no versions detected, using latest commit WARN[0007] no published release discovered for wallabag +-----------------+----------+-------------+------------------------+----------+ | SERVER | RECIPE | CONFIG | DOMAIN | VERSION | +-----------------+----------+-------------+------------------------+----------+ | aadils.computer | wallabag | compose.yml | pocket.aadils.computer | 3da361aa | +-----------------+----------+-------------+------------------------+----------+ ? continue with deployment? Yes INFO[0010] Creating network pocket_aadils_computer_internal FATA[0010] service app: secret not found: pocket_aadils_computer_db_password_v1 ``` may be related to #1?
Owner

Ah, I think #1 is something else but realllly looks like it is the cause 🙃 It is related tho (we'll come back to this). To start fixing this, you need to change the following (3da361aa2e/.env.sample (L8-L9)):

DB_PASSWORD_VERSION=v1
DB_ROOT_PASSWORD_VERSION=v1

To:

SECRET_DB_PASSWORD_VERSION=v1
SECRET_DB_ROOT_PASSWORD_VERSION=v1

Because abra looks for SECRET_... env vars for versioning secrets.

Don't forget to abra app secret generate ...

If you're feeling generous you could fix this in upstream and push a fix to https://git.coopcloud.tech/coop-cloud/wallabag/src/branch/main/.env.sample to add the SECRET_... prefixes 🙏

Now, back to #1, you'll notice this comment in 3da361aa2e/compose.yml (L13-L15) which is saying "you need to put DB_PASSWORD=...in your.envto setup the password for wallabag. This is bad because your password is in plain text in a.env` file but the upstream image doesn't support anything better right now.

Let me know if anything is unclear!

Ah, I think #1 is something else but realllly looks like it is the cause 🙃 It is related tho (we'll come back to this). To start fixing this, you need to change the following (https://git.coopcloud.tech/coop-cloud/wallabag/src/commit/3da361aa2e828636deaa32aeafec1b1598be959a/.env.sample#L8-L9): ``` DB_PASSWORD_VERSION=v1 DB_ROOT_PASSWORD_VERSION=v1 ``` To: ``` SECRET_DB_PASSWORD_VERSION=v1 SECRET_DB_ROOT_PASSWORD_VERSION=v1 ``` Because `abra` looks for `SECRET_...` env vars for versioning secrets. Don't forget to `abra app secret generate ...` If you're feeling generous you could fix this in upstream and push a fix to https://git.coopcloud.tech/coop-cloud/wallabag/src/branch/main/.env.sample to add the `SECRET_...` prefixes 🙏 Now, back to #1, you'll notice this comment in https://git.coopcloud.tech/coop-cloud/wallabag/src/commit/3da361aa2e828636deaa32aeafec1b1598be959a/compose.yml#L13-L15 which is saying "you need to put DB_PASSWORD=...` in your `.env` to setup the password for wallabag. This is bad because your password is in plain text in a `.env` file but the upstream image doesn't support anything better right now. Let me know if anything is unclear!
aadil closed this issue 2022-06-14 10:16:44 +00:00
aadil reopened this issue 2022-06-14 10:23:29 +00:00
Author
Owner

@decentral1se I updated the .env.sample on git, don't know to add it to a release tho

@decentral1se I updated the .env.sample on git, don't know to add it to a release tho
Author
Owner

This works now? Am not sure what changed but 🚀

This works now? Am not sure what changed but 🚀
aadil closed this issue 2023-01-22 10:35:30 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/wallabag#2
No description provided.