You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
Hi. I'm using the new secret type aws_secrets_manager. It seems not to cast string secret values correctly. Especially if the value is a sequence of numbers set as string.
For example having the following AWS secret as JSON:
I had similar issue when using Helm to deploy.
Double quotes are removed from created configmap for vector config.
This results in config values without quotes like this .
A note for the community
Problem
Hi. I'm using the new secret type aws_secrets_manager. It seems not to cast string secret values correctly. Especially if the value is a sequence of numbers set as string.
For example having the following AWS secret as JSON:
With the following configuration
I get the following error at vector startup:
Configuration
No response
Version
0.38.0
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: