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

👍 1 👀 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

Sign in to join this conversation.

1 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