abra app ls -S shouldn't fail if a single .env file is missing
#560
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In alakazam we have a command to do a
psover all our instances and apps. It usesabra app ls -S -s <INSTANCE> -min 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 existIn 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
@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
.envis missing for a deployed app. Is there something I'm missing?Are you still able to reproduce this error on latest
abraand can you provide--debuglogs?OK, merged that test and still can't reproduce. I'm gonna close off for now but if you see it again, please do let me know!
--debuglogs in that case would be great also.