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.81

Develop > HPE Codar command line interface commands > Package commands > List application packages

List application packages

Lists all available application packages for the specified application design.

Command	Alias	Syntax
package list	pkg list	package list -did <designID> [-stage <stage>] [-start <start>] [-page <page>]

Options

Option	Description
`-did, --<designID>`	Application design ID. Use the List application designs command to obtain the design ID.
`-stage, --<lifecycleStage`>	Name of the life cycle stage.
`-start , --<startIndex>`	Specifies the offset of the first entry to be included in the page.
`-page, --<pageSize>`	Specifies the page size.
`-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

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 list –did ff319835-99d0-4205-a89a-6e5d328e5355
name            ID                                   stage          state

Package 5    3c83e586-06de-4ccd-b9a8-c0ffe192d52b    DEVELOPMENT    ACTIVE
Package 3    cdf95956-85ce-46f1-bf74-ed201650aa61    DEVELOPMENT    ACTIVE
Package 2    faa53cdc-5cb2-479f-938b-6eb6552f5ff5    DEVELOPMENT    ACTIVE
Package 1    ca3214ae-6ce9-4dd7-8beb-1713b7542b66    TESTING        ACTIVE

Send Help Center feedback