Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Application Release Automation1.90

Develop > HPE Codar command line interface commands > Package commands > Create an application package

Create an application package

Creates an application package.

Command	Alias	Syntax
package create	pkg create	package create -name <name> -desc <description> -did <designID> [-in <input-file>]

Options

Option	Description
`-did, --<designID>`	Application design ID. Use the List application designs command to obtain the design ID.
`-name, --<name>`	Name of the package.
`-desc, --<description>`	Package description.
`-in, --<input-file>`	Input file containing properties of the application package. If there is already a package for the design, use the List application designs command to obtain the JSON from the existing package and change the value of the attributes.
`-s, --server`	The URL of the HCM ARA instance. For example, https://localhost:8444/csa.
`-u, --user`	The HCM ARA username.
`-p, --password`	The password for the HCM ARA user.
`-c, --config`	A file that contains default general option values in the format “<name>=<value>“, where <name> is “server”, “user”, or “password”. If not specified, the `cliforcodar.properties` file in the home directory of the current user is used if it exists.

Usage guidelines

When creating a package for the first time, use the name and description parameters. Properties from the design are associated to the package by default. The properties of the package can be specified as an input file in JSON format. For sample JSON input format use the List application packages command to obtain the properties of any existing package and modify the values of the package appropriately.

Note: Only the property’s value can be modified.

This command must be pre-defined in a configuration file or defined in the command line. The --server(-s) option defaults to localhost value(s) if it is not pre-defined in a configuration file.

Example

  C:\CODAR\clis> codarexec.bat pkg create -did cb335b9b-aa57-4150-a6c5-a54f80401fde  -name package1 -desc packagedescription –in packageproperties.json

Package 'package1' was added with id 'e44cd095-aa35-468a-81bb-a1c0a36ae959'

Send Help Center feedback