-
Notifications
You must be signed in to change notification settings - Fork 74
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
s3 provider not parsing JSON #114
Comments
@pimguilherme YAML is a superset of JSON so even though there isn't a specific JSON unmarshalling code in vals, our YAML unmarhsalling code should unmarshal your JSON data just fine! |
Here's the part of the s3 provider that does json/yaml parsing Lines 72 to 85 in 332f488
|
thanks for reaching out @mumoshu ! I was trying to pull a list of strings from a tfstate file in AWS S3.. I did some tests now and realized we can only pull values that are text, no numbers or anything else:
In my example back when this ticket was open, I was looking to get the JSON version of whatever was in the key.. I guess this is just not a feature, as desgined.. but would it make sense? 😅 thanks!! |
Triaging an issue almost an year later 🤦 If anyone is still reading this issue and interested in contributing a patch- PR is always welcomed! |
Handles int and bool types when returned as string map value. Resolves: helmfile#114 and helmfile#190
Handles int and bool types when returned as string map value. Resolves: helmfile#114 and helmfile#190 Signed-off-by: Bernardo Salazar <[email protected]>
Hi dear maintainers!
It looks like the s3 provider does not parse JSON as described on the docs.. I have successfully parsed a YAML file but not a JSON file using the
vals eval
commandbrowsing the code we can see that there doesn't seem to be any json unmarshalling other than in google sheets provider
Could you please confirm if this is really the case?
Cheers!
The text was updated successfully, but these errors were encountered: