-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[FEATURE]: Make sink file optional when using agent caching #6452
Comments
You don't need to specify a file sink. Did you set https://www.vaultproject.io/docs/agent/caching/index.html#use_auto_auth_token-bool-false- ? |
I did...
|
Looking into this -- this was supposed to be enabled by #6421 |
It works for me:
Can you post your full config and vault output please? |
@ncabatoff You don't have an auto-auth block. I think the issue may be that if an auto auth block exists but there are no sinks then it doesn't like it. |
Ah, yes, you're right. I didn't consider that use case when I made my changes. Should be easy to fix. |
Thats seems to be it based on the log error Tks guys |
Since the Vault Agent Caching is already running as a daemon, it would be great if it also cached the Auth Token in-memory instead of storing it in a file. This way the Auth Token is not exposed anywhere.
I know we have the option to store it in a tmpfs so the sink file never touches the disk, but still it would be a file with the auth token accessible somehow. Having the Vault Agent fully accountable to manage the auth token would be great for our use-case.
The text was updated successfully, but these errors were encountered: