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
secrets-env with no arguments should get all secrets for whatever repo the current working directory is inside.
The only reason to be omitting arguments is to save typing when running interactively; build scripts can afford lots of arguments. I think showing the secrets for the current repo and stage is a sensible default.
This should not work outside a repo; attempting to do so should display an error.
It should also be possible to omit the namespace but provide a stage, in order to view secrets for the current repo but a different stage.
The text was updated successfully, but these errors were encountered:
secrets-env
with no arguments should get all secrets for whatever repo the current working directory is inside.The only reason to be omitting arguments is to save typing when running interactively; build scripts can afford lots of arguments. I think showing the secrets for the current repo and stage is a sensible default.
This should not work outside a repo; attempting to do so should display an error.
It should also be possible to omit the namespace but provide a stage, in order to view secrets for the current repo but a different stage.
The text was updated successfully, but these errors were encountered: