may be we could pass parameter to script by name

[yosefy]

because when there are too many it becomes pretty complicated to remember numbers

may be there is such an option?

(i can live without it... just a thought)
thanks

[bugy]

Hi @yosefy could you explain in examples, please, what do you mean?
I'm not sure which numbers you are talking about

[yosefy]

there is a name for each parameter

{
  "name": "choose_environment",
  "param": "--env",
  "description": "Environment",
  "required": true,
  "type": "list",
  "default": "dev",
  "values": [
    "dev",
    "prod"
  ]
}

then in the script
cd "/mydir/$choose_environment/path"

[yosefy]

insted of
cd "/mydir/$1/path"

[yosefy]

or may be we could use the "param" without dashes as name

[bugy]

To be honest I'm confused. How are you using "param": "--env",?
And I guess in your example, you should reference the variable by $2 and not $1, right?
(I'm asking because I don't really understand the example).

But in general, as far as I understand, you would like that Script server will create environment variables based on parameters (and their) and pass them to a script, is it correct?
I think it would be possible, with replacing of unsupported characters (e.g. spaces)

Also Script server is based on the vision, that nobody will have a need to adjust their scripts for Script server :) And with this variables, your script would be almost unusable outside of Script server
Though for me this is not a problem. If you would like to adjust your script, it shouldn't be discouraged

[yosefy]

actually i am building my scripts for script-server in my case
so i think the best would be to turn

--test to "TEST"
--simple-bool to "SIMPLE_BOOL" and pass to script
(everything not a-z will turn to "_" )
then inside the script we don't have to remember what ${78} means :)

i think may be "param" is best candidate for the var name because it cant have spaces in it anyway
and if there is no param, no var

so that way scripts can continue running without script-server and still be logically connected to this way

may be you have better idea?

but again it is only for improvement. i am happy with script server anyway :)

[bugy]

I would use parameter name instead, because "param" should be used in a diferent manner (and it could be a single letter in a lot of cases).

But are you using "param" in your scripts at all? If you access parameters by index, then you don't need it.
I'm referring to this approach of using param: https://stackoverflow.com/a/14203146/2166673

Anyway, the idea itself makes sense

[yosefy]

amm i don't use it like this in this case (mostly using script server with ansible and terraform and packer for now)
about param you are right it is single latter sometimes
not sure need to add more fields put ok too
may be "name" is good candidate?

[bugy]

Name should be ok.

amm i don't use it like this in this case

But then you can skip specifying param all the time. It's not required :)

[yosefy]

yes i know but still you have to remember what is this $4 (or was it $3??) you see in the script
instead of $MEANINGFULL_NAME

example from real life :)

[bugy]

I agree with you, the whole ticket makes perfect sense.

By the way, why don't you set variables at the beginning of the script? It will make your life a little bit easier, I guess. Example:

#!/bin/bash

environment="$1"
user="$2"
command="$3"

cd "/mydir/$environment/path"

[yosefy]

well also an option :)

also to let you know
in ansible there is -e (external var) option, which you may add more then once
so in script-server this -e flags adds itself when the var is defined together with var(very useful!)

it solves many problems of not knowing the exact amount of vars that will be there in the end

so just wanted to thanks for that :)

[yosefy]

so another reason:

terraform apply -var "env=dev" -var "app=test" -var "size=6"

and i don't know how many there will be as they come from dynamically included config files for example

so, if "app" is not required and not set, then "size" will move from $6 to $4
and it may cause disaster :)

same with running ansible with multiple -e option or any other software of this type

so if we only use it with terraform command , then ok, we just add them all
BUT if in a script i wan't to run some other checks for example then i need to know the exact index
of the variable

so here turning name to ENV VAR as you suggested may fix the situation completely

thanks

[yosefy]

ok after trying all day :) need help
i want to do this
terraform apply $@
and that shoud do:
terraform apply -var env=dev -var app=test -var size=6 -var last_unknown=x

but i don't i can't find a way to do it
if i add param: "-var env="
then i get -var env= prod (with space)

@bugy , may be you have some idea?
thanks