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

Parse JSON formatted values, coming from the scripts #189

Open
yosefy opened this issue Feb 27, 2019 · 3 comments
Open

Parse JSON formatted values, coming from the scripts #189

yosefy opened this issue Feb 27, 2019 · 3 comments
Labels

Comments

@yosefy
Copy link

yosefy commented Feb 27, 2019

lots of lists are coming from some api in json format, i have wrote a wrapper script with curl
but may be good idea to add another values type for that...

  "values": {
          "web-request": "http://some-api.com"
  }

which will return ["a", "b", "c", "d"]

wrapper for now is

      "values": {
              "script": "wrapper.sh 'http://something.com'"
      }
#!/bin/bash

#wrapper.sh

res=`curl -s $1 | tr -d "[" | tr -d "]" | tr ',' '\n' | tr -d '"'`
echo "$res"

thanks

@bugy bugy added the feature label Feb 27, 2019
@bugy
Copy link
Owner

bugy commented Feb 27, 2019

Hi @yosefy, thanks for proposal. It makes sense

However the ticket title is confusing

@yosefy yosefy changed the title some sign that the variable is loading add visual representation that the variable is loading from script Feb 27, 2019
@yosefy
Copy link
Author

yosefy commented Feb 27, 2019

amm i hope it is better :)

@bugy
Copy link
Owner

bugy commented Feb 27, 2019

Hi @yosefy, I guess this is a title for a wrong issue :) From the description, it should be something like: "Parse JSON formatted values, coming from the scripts"

@yosefy yosefy changed the title add visual representation that the variable is loading from script Parse JSON formatted values, coming from the scripts Feb 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants