Hi Jay, I would recommend you to use GlobalVariables instead of script parameters due to a couple reasons:
1. GlobalVariables are translated into ENV variables and it's much easier to test scripts. 2. GlobalVariables has flags that can help you to make this mandatory, set defaults, etc.. 3. Scripting parameters will be deprecated and removed in future versions of Scalr. Regards, Igor On 13 April 2016 at 15:57, Jay Farschman <[email protected]> wrote: > This should be simple, and I think I once understood it, but I cannot find > the answer now. > > I'm writing a script to install Java JDK on systems and what the users to > enter a version number > > # Available versions 8u77 - Older 11 20,25,31,45,51,66,77 > : ${version:=%java_version%} > : ${app_dir:="/usr/lib/java"} > : ${conf_dir:="/etc/java"} > : > ${packagerepo_path:="https://s3-us-west-2.amazonaws.com/bucket/path/to/binaries"} > > Later in the script I curl the binary and install it. > > PROBLEM > I thought I could make %java_version% a required variable were the user > could not. Instead, it's seems like adding %java_version% is optional. > > QUESTIONS > Can I make it a required parameter before the instance will save or start? > Can I set a default and let them override it? > > I like both of those methods and would use them at different times if they > are available. Oh... and I can share this script if anyone needs something > like it. You'd have to manage your own packagerepo, but that's pretty easy. > > -- > You received this message because you are subscribed to the Google Groups > "scalr-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
