Synopsis

fcli fod app create [--auto-required-attrs] --criticality=<criticalityType> [-d=<description>] [--delim=<delimiter>] --owner=<owner> --release=[ms:]rel [--release-description=<releaseDescription>] --status=<sdlcStatusType> --type=<appType> [,[ATTR=VALUE]…​]]…​ [--groups=<userGroups>_[, <userGroups>…​]]…​ [--notify=<notifications>[, <notifications>…​]]…​ [[-h] [--env-prefix=<envPrefix>] [--log-file=<logFile>] [--log-level=<logLevel>]] [[--session=<sessionName>]] ] [--store=_variableName[=<propertyNames>]] [--to-file=<outputFile>]] <applicationName>

Description

This command allows a new application and its first release to be created. Please note some attributes might be mandatory depending on the configuration of your tenant. Please check the Fortify on Demand web portal first.

Options

--attrs, --attributes=[ATTR=VALUE][,[ATTR=VALUE]…​]

Attribute id or name and its value to set on the application.

--auto-required-attrs

Automatically set a default value for required attributes.

--criticality, --business-criticality=<criticalityType>

The business criticality of the application. Valid values: High, Medium, Low.

-d, --description=<description>

Description of the application.

--delim=<delimiter>

Change the default delimiter character when using options that accept "application[:microservice]:release" as an argument or parameter.

--groups=<userGroups>[,<userGroups>…​]

User group ids or names to give access of the application to.

--notify=<notifications>[,<notifications>…​]

Email address of user(s) to send notifications to.

--owner=<owner>

The owner of the application/release who will receive email notifications of scan status update.

--release=[ms:]rel

Initial release to be created on the application, in the format <microservice>:<release> for a microservices application, or just <release> for non-microservices applications.

--release-description=<releaseDescription>

Description of the release.

--status, --sdlc-status=<sdlcStatusType>

The SDLC lifecycle status of the release. Valid values: Development, QA, Production

--type, --app-type=<appType>

Application type. Valid values: Web, ThickClient, Mobile, Microservice

Session options:

--session=<sessionName>

Name of the FoD session to use for executing this command. Default value: default.

Output options:

-o, --output=format[=<options>]

Specify output format and options. Available output formats: csv, csv-plain, json, json-flat, table, table-plain, tree, tree-flat, xml, xml-flat, yaml, yaml-flat, expr, json-properties. The 'expr' output format takes a string containing '{property}' placeholders, other output formats take an optional, comma-separated list of properties to include in the output. Use '-o json-properties' on the current command to see available properties.

--store=variableName[=<propertyNames>]

Store the JSON results of this command in a variable. Variables can be managed through the 'fcli util variable' command, and can be referenced using ::variable::[property] on any subsequent command.

--to-file=<outputFile>

Write command output to the specified file instead of stdout.

Generic fcli options:

--env-prefix=<envPrefix>

Environment variable prefix for resolving default option and parameter values. Default value is FCLI_DEFAULT.

-h, --help

Show this help message and exit. Use 'fcli <command> -h' to display help for subcommands.

--log-file=<logFile>

File where logging data will be written. Defaults to fcli.log in current directory if --log-level is specified.

--log-level=<logLevel>

Set logging level. Note that DEBUG and TRACE levels may result in sensitive data being written to the log file. Allowed values: TRACE, DEBUG, INFO, WARN, ERROR.

Arguments

<applicationName>

Application name.