Abra should remind running app secret #609

New Issue

basebuilder · 2024-04-15T08:58:25Z

basebuilder commented

2024-04-15 08:58:25 +00:00

Currently when creating a new app abra app new is helpful enough to prompt with the next two sub-commands config and deploy

user@dev:~$ abra app new sextant
? Select app server: sextant.eotl.supply
? Specify app domain sextant.eotl.supply
A new sextant app has been created! Here is an overview:

+-------------+---------+-------------------+
|   SERVER    | RECIPE  |      DOMAIN       |
+-------------+---------+-------------------+
| eotl.supply | sextant | sextant.eotl.supply |
+-------------+---------+-------------------+


You can configure this app by running the following:

    abra app config sextant.eotl.supply

You can deploy this app by running the following:

    abra app deploy sextant.eotl.supply

However, if an app requires secret generate step, this is incorrect and needs to be done before running deploy step.

Perhaps we can make abra smart enough to look if an app config requires secrets and then it shows the following:

...

You can then configure secrets with:

    abra app secret generate -a sextant.eotl.supply

You can deploy this app by running the following:

    abra app sextant.eotl.supply

Currently when creating a new app `abra app new` is helpful enough to prompt with the next two sub-commands `config` and `deploy` ``` user@dev:~$ abra app new sextant ? Select app server: sextant.eotl.supply ? Specify app domain sextant.eotl.supply A new sextant app has been created! Here is an overview: +-------------+---------+-------------------+ | SERVER | RECIPE | DOMAIN | +-------------+---------+-------------------+ | eotl.supply | sextant | sextant.eotl.supply | +-------------+---------+-------------------+ You can configure this app by running the following: abra app config sextant.eotl.supply You can deploy this app by running the following: abra app deploy sextant.eotl.supply ``` However, if an app requires `secret generate` step, this is incorrect and needs to be done *before* running `deploy` step. Perhaps we can make `abra` smart enough to look if an app config requires secrets and then it shows the following: ``` ... You can then configure secrets with: abra app secret generate -a sextant.eotl.supply You can deploy this app by running the following: abra app sextant.eotl.supply ```

👍 2

basebuilder added the

enhancement

label 2024-04-15 08:58:25 +00:00

decentral1se added the

abra

label 2024-06-22 12:52:20 +00:00

decentral1se added this to the Abra v0.11.x project 2025-08-29 10:28:10 +00:00

decentral1se moved this to In Progress in Abra v0.11.x on 2025-08-30 10:04:54 +00:00

decentral1se referenced this issue from toolshed/abra

2025-08-30 10:27:55 +00:00

feat: warn for secret generation #634

decentral1se commented

2025-08-30 10:29:21 +00:00

The output became a lot less wordy in the meantime.

Here's a sample output:

> ./abra app new gitea
INFO single server detected, choosing test.foo.org automatically
? Specify app domain gitea.test.foo.org
INFO gitea.test.foo.org created (version: 3.5.1+1.24.2-rootless)
WARN gitea requires secret generation before deploying, run "abra app secret generate gitea.test.foo.org --all"

The output became a lot less wordy in the meantime. Here's a sample output: ```bash > ./abra app new gitea INFO single server detected, choosing test.foo.org automatically ? Specify app domain gitea.test.foo.org INFO gitea.test.foo.org created (version: 3.5.1+1.24.2-rootless) WARN gitea requires secret generation before deploying, run "abra app secret generate gitea.test.foo.org --all" ```

❤️ 1

decentral1se closed this issue

2025-08-30 10:29:21 +00:00

decentral1se moved this to Done in Abra v0.11.x on 2025-08-30 10:29:31 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/organising#609