Skip to content
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

Open
pimguilherme opened this issue Dec 12, 2022 · 4 comments
Open

s3 provider not parsing JSON #114

pimguilherme opened this issue Dec 12, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@pimguilherme
Copy link

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 command

browsing 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!

@mumoshu
Copy link
Collaborator

mumoshu commented Feb 4, 2023

@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!
Could you give us a full reproduction example?

@mumoshu
Copy link
Collaborator

mumoshu commented Feb 5, 2023

Here's the part of the s3 provider that does json/yaml parsing

func (p *provider) GetStringMap(key string) (map[string]interface{}, error) {
yamlData, err := p.GetString(key)
if err != nil {
return nil, err
}
m := map[string]interface{}{}
if err := yaml.Unmarshal([]byte(yamlData), &m); err != nil {
return nil, err
}
return m, nil
}

@pimguilherme
Copy link
Author

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:


$ echo 'test_plain_yaml: ref+s3://teste-s3fs/test.yml?profile=homolog' | vals eval -f -
s3: successfully retrieved object for key=teste-s3fs/test.yml
test_plain_yaml: |
  key: 456

$ echo 'test_plain_json: ref+s3://teste-s3fs/test.json?profile=homolog' | vals eval -f -
s3: successfully retrieved object for key=teste-s3fs/test.json
test_plain_json: |
  {
  	"key": 123
  }

$ echo 'test_json_key: ref+s3://teste-s3fs/test.json?profile=homolog#/key' | vals eval -f -
s3: successfully retrieved object for key=teste-s3fs/test.json
expand s3://teste-s3fs/test.json?profile=homolog#/key: no value found for key key

$ echo 'test_yaml_key: ref+s3://teste-s3fs/test.yml?profile=homolog#/key' | vals eval -f -
s3: successfully retrieved object for key=teste-s3fs/test.yml
expand s3://teste-s3fs/test.yml?profile=homolog#/key: no value found for key key

# changed the values to text

$ echo 'test_yaml_key: ref+s3://teste-s3fs/test.yml?profile=homolog#key' | vals eval -f -
s3: successfully retrieved object for key=teste-s3fs/test.yml
test_yaml_key: "456"
$ echo 'test_json_key: ref+s3://teste-s3fs/test.json?profile=homolog#/key' | vals eval -f -
s3: successfully retrieved object for key=teste-s3fs/test.json
test_json_key: "123"

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!!

@mumoshu mumoshu added the bug Something isn't working label Dec 1, 2023
@mumoshu
Copy link
Collaborator

mumoshu commented Dec 1, 2023

Triaging an issue almost an year later 🤦
Thanks for your detailed report @pimguilherme! I consider this as a bug- not sure what's causing it but it isn't what I expected.

If anyone is still reading this issue and interested in contributing a patch- PR is always welcomed!

bersalazar added a commit to bersalazar/vals that referenced this issue Dec 31, 2023
Handles int and bool types when returned as string map value.

Resolves: helmfile#114 and helmfile#190
bersalazar added a commit to bersalazar/vals that referenced this issue Dec 31, 2023
Handles int and bool types when returned as string map value.

Resolves: helmfile#114 and helmfile#190
Signed-off-by: Bernardo Salazar <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants