Hi, I'm trying to run vault-unseal as container in my docker swarm instance.
Then I realize to make it work I need to store my tokens in unencrypted format inside the vault-unseal.yaml file in the host.
I think it would be very nice if the vault-unseal support reading token list from separate file, so I can then use docker secrets to store my tokens securely.
š§ Is your feature request related to a problem?
No response
š Describe alternatives you've considered
--
ā If implemented, do you think this feature will be a breaking change to users?
Yes
ā Additional context
To make my approach of using vault-unseal clearer, here is the example.
First I create new secret containing the tokens:
echo "aaaaaaaaaaaaaaaaaa,bbbbbbbbbbbbbbb" | docker secret create vault_unseal_tokens_a_b -
Then I can use the stack compose script below to easily spawn new vault-unseal node:
āØ Describe the feature you'd like
Hi, I'm trying to run vault-unseal as container in my docker swarm instance. Then I realize to make it work I need to store my tokens in unencrypted format inside the
vault-unseal.yaml
file in the host.I think it would be very nice if the vault-unseal support reading token list from separate file, so I can then use docker secrets to store my tokens securely.
š§ Is your feature request related to a problem?
No response
š Describe alternatives you've considered
--
ā If implemented, do you think this feature will be a breaking change to users?
Yes
ā Additional context
To make my approach of using vault-unseal clearer, here is the example.
First I create new secret containing the tokens:
echo "aaaaaaaaaaaaaaaaaa,bbbbbbbbbbbbbbb" | docker secret create vault_unseal_tokens_a_b -
Then I can use the stack compose script below to easily spawn new vault-unseal node:
š¤ Requirements