Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parse error on empty secrets file #144

Open
isomorpheme opened this issue Nov 20, 2024 · 0 comments · May be fixed by #145
Open

Parse error on empty secrets file #144

isomorpheme opened this issue Nov 20, 2024 · 0 comments · May be fixed by #145

Comments

@isomorpheme
Copy link

isomorpheme commented Nov 20, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant