Closed timurkhisamov closed 1 year ago
I'm seeing similar behavior with the service_registration "consul"
stanza on Vault 1.11.2
I did a little more investigating and it seems Vault accepts the JSON configuration and the warning is spurious. (To be clear, this should be fixed to prevent confusion.) In my case, I was using the gcpckms
seal and the consul
service registration. I was able to confirm that it was still using the GCP KMS key and registering with Consul.
Hi folks! Just wanted to leave a little update here. I believe I've found the source of the problem. I can confirm that the warnings are spurious and that a fix will be coming soon.
In particular, this affects json configuration like this:
"foo": {
"bar": {
"baz": "xyz"
}
}
and it will in some cases produce a spurious warning about bar
.
Closing this issue, as this should be fixed by https://github.com/hashicorp/vault/pull/17660
Thanks for the report! I appreciated the detail.
awskms
field didn't parsed when configs are stored in JSON format When I use JSON format to store our configurations, I found in logs next:JSON configs:
But when I use HCL format, error didn't reproduce:![image](https://user-images.githubusercontent.com/60743672/188422814-5291e052-f366-4abd-9e21-6806f885442d.png)
HCL configs:
To Reproduce Steps to reproduce the behavior:
awskms
unsealing option.Expected behavior A clear and concise description of what you expected to happen.
Environment:
vault status
):vault version
):