Set

The command help is shown below.

Usage: qaskx-cli rediops set -s=<section> --tag=<name> [--platform=<platform>] --value=<JSON payload or single text> [-d=<devops file path>] [-f=<format>] [-o=<output file>] [-v | --vv | --vvv | --silent] [-c=<conf file>] [--colourCLI] [--offline] [--env=<environment file>]

The rediOps set command updates certain details in the definition
file. 
			
The command will output the results to the console or an output file

For more details see the documentation at https://docs.qaskx.one/qaskx-cli/cmd/rediops//set/ .

                    
Options:            
  -d, --devops      rediOps (devops.json) file path
  -s, --section     Definition section (e.g. ID,REPOSITORY,API,DEPENDENCY,BUILD)
      --tag         Definition identifier (default "*ANY")
      --platform    Platform for execution (default "windows")
      --value       Data value in JSON format or *prompt
  -o, --output      Output file name (default "CONSOLE")
  -f, --format      Output format [PRINT,TAB, CSV] (default "PRINT")
      --overwrite   Overwrite existing content
  -v, --verbose     Verbose logging
      --vv          Verbose logging level 3
      --vvv         Verbose logging level 5
      --silent      Silent running
      --colourCLI   Colour terminal and command line (env $QASKX_COLOUR_CLI)
  -c, --conf        Configuration file (env $QASKX_CONFIG_FILE)
      --offline     Offline mode (env $QASKX_OFFLINE)
      --env         Environment file to use (default ".env")

Details

The “set” subcommand is used to add or modify existing values in the rediOps file devops.json.

When using the command the –tag argument is used to match with existing data in the selected section specified by the –section value. If no match is found then a new record is inserted into the rediOps specification file.

The tag value is the identifier for the record, and is dependant on section.

The tag identifier fields by section are:

  1. REPOSITORY - the Name
  2. API - the Service identifier
  3. DEPENDENCY- the Service identifier
  4. BUILD - the Identifier
  5. TEST - the Identifier
  6. DEPLOY / INSTALL - the Identifier
  7. RELEASE - not applicable
  8. TOOL - the Service Identifier
  9. ID - not applicable
  10. BASE - not applicable
  11. GUIDES - not applicable

There are two options for supplying the new values:

  1. As a json string supplied in –value
  2. User prompts with the special directive *prompt supplied in –value