Is your feature request related to a problem? Please describe.
Given a config like this:
{
"auto_auth": {
"sink": [
{
"config": {
"mode": 256,
"path": "/run/keys/my-token"
},
"type": "file"
}
]
}
}
Note the 256 is to work around #9404.
The /run/keys/my-token file is deleted and recreated with the owner / group running the Vault agent. This is different from the templating support, which will preserve the owner and group of the existing file.
Describe the solution you'd like
I would like to specify the owner and group of the sink file, or, have the sink preserve the ownership.
Describe alternatives you've considered
Running vault login in a loop to create the file instead.
Is your feature request related to a problem? Please describe.
Given a config like this:
Note the 256 is to work around #9404.
The
/run/keys/my-tokenfile is deleted and recreated with the owner / group running the Vault agent. This is different from the templating support, which will preserve the owner and group of the existing file.Describe the solution you'd like
I would like to specify the owner and group of the sink file, or, have the sink preserve the ownership.
Describe alternatives you've considered
Running
vault loginin a loop to create the file instead.