pcl-configure - Change configuration of an application


pcl configure [-eq] [--deploy] [-a=<applicationName>] [-n=<namespaceName>] [-o=<outputFormat>] [-s=<subscriptionName>] [-t=<timeout>]


Change configuration of an application Configuration is different for each application. In order to discover which configuration kinds for an application are available, invoke pcl configuration -n $namespace -a $app configure --help. In order to learn about keys and configuration ids available for specific kind invoke pcl configuration -n $namespace -a $app configure $kind --help. It is possible to chain setting values of multiple configuration kinds in single command.


-a, --application=<applicationName>

Name of application to manage.

Not required for commands listed by -n option, as well as list-applications and upload.


Deploy revision with updated configuration immediately

-e, --fail-early

Fail command immediately after first deployment problem instead of waiting for timeout on client or backend side

There are certain scenarios when deployment can succeed despite deployment problems reported.

It is therefore not guaranteed that application deployment that failed with early warning will not start up later.

-n, --namespace=<namespaceName>

Name of namespace to manage.

Required for all commands except login, list-namespaces and create-namespace.

-o, --output=<outputFormat>

Output format. Allowed values: TEXT, JSON.

-q, --quiet

Quiet output.

Only result of operations will be displayed to stdout, or error message to stderrr.

-s, --subscription=<subscriptionName>

Name of subscription to use. Only necessary when account has access to multiple subscriptions.

-t, --timeout=<timeout>

Duration in seconds specifying how long to wait for deployment to complete

This is client side timeout which doesn’t affect deployment process in Payara Cloud. It is therefore not guaranteed that application deployment that failed due to this time out will not eventually start up later.