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
In a project, I already added some placeholder secrets files that are empty, just to already add a call to vaultenv in automation but without requesting any secrets yet. But the parser chokes on that:
$ touch nothing-to-hide.secrets
$ vaultenv --secrets-file nothing-to-hide.secrets -- echo'i am an open book'
[ERROR] nothing-to-hide.secrets:1:1:
|
1 |<empty line>| ^
unexpected end of input
expecting "VERSION", newline, or path component
This might be a silly use case, but I think "actually, I don't need any secrets" should still be a valid input.
The text was updated successfully, but these errors were encountered:
In a project, I already added some placeholder secrets files that are empty, just to already add a call to
vaultenv
in automation but without requesting any secrets yet. But the parser chokes on that:This might be a silly use case, but I think "actually, I don't need any secrets" should still be a valid input.
The text was updated successfully, but these errors were encountered: