abra no longer able to deploy rstudio, secret name mismatch #532

New Issue

3wordchant · 2023-11-07T23:41:30Z

3wordchant commented

2023-11-07 23:41:30 +00:00

FATA[0001] unable to deploy, secrets not generated (keycloak_client_secret)

After adding some more debug output, it's looking for a secret called rstudio-431_washnote_org_keycloak_client_secret_secret.

This is despite SECRET_KEYCLOAK_CLIENT_SECRET_VERSION=v1 in the .env, and also despite the secret being overridden by another compose file.

So I guess this is 2 issues:

Why is abra looking for <stack name>_<secret>_secret, i.e. assuming secret is the version?
How can we make abra look at the final secret name, including compose file overrides, instead of assuming every secret name will have a version?

`FATA[0001] unable to deploy, secrets not generated (keycloak_client_secret)` After adding some more debug output, it's looking for a secret called `rstudio-431_washnote_org_keycloak_client_secret_secret`. This is despite `SECRET_KEYCLOAK_CLIENT_SECRET_VERSION=v1` in the `.env`, and also despite the [secret being overridden by another compose file](https://git.coopcloud.tech/coop-cloud/rstudio/src/branch/main/compose.keycloak-sharedsecret.yml). So I guess this is 2 issues: 1. Why is `abra` looking for `<stack name>_<secret>_secret`, i.e. assuming `secret` is the version? 2. How can we make `abra` look at the final secret name, including compose file overrides, instead of assuming every secret name will have a version?

3wordchant added the

bug

label 2023-11-07 23:41:30 +00:00

moritz commented

2023-11-21 13:00:33 +00:00

I think it's the same as coop-cloud/organising#464

I think it's the same as https://git.coopcloud.tech/coop-cloud/organising/issues/464

3wordchant commented

2023-11-22 15:54:04 +00:00

Yep seems so, thanks for help triaging, @moritz

3wordchant closed this issue

2023-11-22 15:54:10 +00:00