Request for YML/DSL syntax improvement: multiline, dictionary (map), or non string values

[rqc]

Hello,

I just wanted to give a bit of feedback on the usability of cloudslang DSL. Here they are;

1. Remove requirement to wrap values for news in double quotes and single quotes. I understand that distinguishing between what is code and what isn't is complicated. But having me for instance, to do this:

 - command: "'echo \"Hello World\"'"

can be very detrimental to productivity and error prone. Instead it would be easier to do something like:

- command: echo "Hello World" 

or at least:

- command: "echo \"Hello World\""

1. Have better cli input flags for run command. Right now, you have to wrap all inputs in double quotes separated by commas, then you have to escape special characters if you use them as values to the input parameters, etc. Again, this is very error prone to use manually and even when you are trying to use this programmatically. My suggestion is have flags that can be repeated like docker run allows multiple -v or -e flags. Maybe have a flag -i that specifies each separate input.
2. It would be good to allow multiline values in input lists for instance:

- command: |
  echo "Hello World"
  echo "Cloudslang is cool"

Not sure if this is allowed by yaml format, but it is worth the investigation.

1. It would also be cool to establish inputs as maps (not sure if this is possible right now in cloudslang). I guess it would require the inputs to be entered as a map itself and not a list:

inputs:
   input_1: 
       key1: value1
       key2: value2
   input_2: "foo"

Thanks!

[meirwah]

Hi @rqc , Did you look at input file capability: http://cloudslang-docs.readthedocs.org/en/v0.8/cloudslang_cli/#run-with-inputs

And we support maps of imputs, take a look at : http://cloudslang-docs.readthedocs.org/en/v0.8/yaml_overview/#maps

@Bonczidai @oritstone you have in mind any map example in our content today?

[levice14]

Hi @rqc , thanks for your feedback!

Some of my comments:

• quotes: agree, we have a discussion regarding double quotes ( #354 ), feel free to jump inthere -- currently you have to use double quotes for strings instead of single quotes (e.g. "'CloudSlang'") because inputs are loaded with Yaml and then evaluated using Python (so you have 2 layers)
• working syntax for map inputs ( https://github.com/CloudSlang/cloud-slang/blob/master/cloudslang-tests/src/test/resources/yaml/loops/simple_loop_with_map.sl#L17 ):

    - person_map: >
        {'john': 1, 'jane': 2, 'peter': 'three'}

[oritstone]

@rqc thanks for you feedback :)

• Regarding the double quotes issue you raised, we are currently debating over what is the best approach to tackle that issue (we have several ideas). We would appreciate it a lot if you can give your feedback. You can refer issue #354 and give us your opinion on the matter
• About passing inputs to the cli - look at http://cloudslang-docs.readthedocs.org/en/v0.8/cloudslang_cli/#run-with-inputs, specifically around passing inputs using input file. It may assist your needs. It is easier to pass inputs this way, including multi-lines, lists or maps. Let us know if you think it is enough

[rqc]

@oritstone thank you for your team's help.

• Regarding the double quotes I will make sure I follow that issue.
• Regarding the CLI, I had seen the capability of the input files and it looks great. However, my suggestion was to improve the UX of the interaction with the CLI. It is ok to use an input file for flows that won't change its inputs constantly, but for those that do, interacting with the CLI with clean commands and options is best.

[oritstone]

Thanks @rqc It is a good idea to improve our CLI UX. We will definitely add it to our roadmap