The name of the variable used in side the command script should be reflected in the option metadata. This is because there are some rules about how an option name is translated into a variable suitable for the shell.
- Upcased. -lowercase, -camelCase => LOWERCASE, CAMELCASE
- Underscored. -one-two-three => ONE_TWO_THREE
options//metadata should contain a new key called VARNAME.
eg. modules//options/jndi-role-base/metadata
NAME=jndi-role-base
DESCRIPTION="the JNDI role base"
VARNAME=JNDI_ROLE_BASE
ARGUMENTS=true
REQUIRED=false
SHORT=
LONG=jndi-role-base
DEFAULT=
EXPORT=false
The name of the variable used in side the command script should be reflected in the option metadata. This is because there are some rules about how an option name is translated into a variable suitable for the shell.
options//metadata should contain a new key called VARNAME.
eg. modules//options/jndi-role-base/metadata