...
- Command Set Parameters
- opConfig now supportsĀ parameterized command sets, eg . Eg: ping $ipaddress
- Parameters can be passed in via the command line, eg . Eg parameters.x
- When creating a new Virtual Operator Job and , if you have selected a command set which has parameters, the form will then display next "Next" and the second screen will ask you to provide parameters
- Parameters can also be passed in through derived data
- parameters Parameters currently have two data types, "string" and "ipaddress"
- ipaddress is just used for front end validation, the cli does no validation
- parameters_required => "true" can be set and if . If the parameters from the cli or gui have not been passed in then , opConfig will not run the command
Parameters get defined by a top level key and are an array of objects with two keys, : parameter and type
Code Block "parameters" : [ { "parameter" : "id", "type" : "String" }, { "type" : "String", "parameter" : "name" } ],
- Command Set Editor under "System" > "Manage Command Sets"
- You can delete, update and create new command sets through a visual GUI
- Only command sets under conf/command_sets.d/ can be modified.
- Derived Data has new types of table columns to display related jobs or create new virtual operator jobs from. Plugins in opConfig#NewDerivedInformationElementsinopConfig4.2.1
- Conditions has new types of table columns to display tags, urls and tooltips, More details can be found here Plugins in opConfig#NewReportConditionElementsinopConfig4.2.1
- New top level key, "active" can be set to "true"/"false" if false the command set wont be loaded
- New key for commands "active" can be set to "true"/"false" if false the command from that set wont be loaded, other commands set to true will be loaded as part of the set.
...