You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2021. It is now read-only.
Supplying an app to the status command will trigger a different flow since a session towards the app will be opened instead to supply info regarding the data model etc.
Not a bug in my opinion since an invalid parameter was passed.
I was more referring to that supplying invalid parameters to a command should result in a fatal error -> exit code 1. At least that is the approach we have for other commands.
As an end-user I would want the command to fail if I had faulty params in e.g. my config, but lets take a discussion on what should be included in the status command. I agree that we need to do a retake on what should be presented.
When running corectl with app in config file, and the app doesn't exist the status command will not give a good response.
corectl -c local-corectl.yaml status
ERROR could not open app with ID '1fa8a65f-855e-4f7c-bbdc-1f81739e1d96': Could not find app: App not found (1003)
Inform that the app doesn't exist, but also print engine information.
The text was updated successfully, but these errors were encountered: