abra app ls -S shouldn't fail if a single .env file is missing #560

New Issue

simon · 2025-05-19T08:16:38Z

simon commented

2025-05-19 08:16:38 +00:00

In alakazam we have a command to do a ps over all our instances and apps. It uses abra app ls -S -s <INSTANCE> -m in the background.

Said command raises the following error, if the server has an app deployed without the respective .env file on the client system.
FATA unable to retrieve tags for <APP>: repository does not exist

In a shared environment, this happens frequently. It'd be nice if the command could still output as much as possible, with a warning for said missing .env file

In [alakazam](https://git.coopcloud.tech/moritz/alakazam) we have a command to do a `ps` over all our instances and apps. It uses `abra app ls -S -s <INSTANCE> -m` in the background. Said command raises the following error, if the server has an app deployed without the respective .env file on the client system. `FATA unable to retrieve tags for <APP>: repository does not exist` In a shared environment, this happens frequently. It'd be nice if the command could still output as much as possible, with a warning for said missing .env file

👍 2 👀 1

decentral1se added the

enhancement

label 2025-05-19 09:03:52 +00:00

decentral1se added this to the Abra "next" project 2025-05-19 09:04:00 +00:00

decentral1se referenced this issue

2025-07-04 13:51:52 +00:00

abra app list -S should not fail if one of the servers is not accessible #581

decentral1se self-assigned this 2025-07-08 09:59:55 +00:00

decentral1se added the

red abya yala

label 2025-07-08 10:02:24 +00:00

decentral1se referenced this issue from a commit

2025-08-12 20:16:15 +00:00

test: check app list doesn't explode if missing .env

decentral1se referenced this issue

2025-08-12 20:16:21 +00:00

test: check app list doesn't explode if missing .env #591

decentral1se commented

2025-08-12 20:21:27 +00:00

@simon coming back to this after ages... sorry for the delay!

I am actually unable to reproduce this. I created an integration test which is passing in #591 and doesn't error out when the .env is missing for a deployed app. Is there something I'm missing?

Are you still able to reproduce this error on latest abra and can you provide --debug logs?

@simon coming back to this after ages... sorry for the delay! I am actually unable to reproduce this. I created an integration test which is passing in https://git.coopcloud.tech/toolshed/abra/pulls/591 and doesn't error out when the `.env` is missing for a deployed app. Is there something I'm missing? Are you still able to reproduce this error on latest `abra` and can you provide `--debug` logs?

decentral1se moved this to In Progress in Abra "next" on 2025-08-12 20:23:30 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#560

abra app ls -S shouldn't fail if a single .env file is missing #560

`abra app ls -S` shouldn't fail if a single .env file is missing #560