DeployGar
The DeployGar program implements a set of command line options for working with Genero archive (.gar) files on a GAS secured by a Genero Identity Provider.
Syntax
DeployGar command [ options ] [ args ]
- command. There are nine commands to perform actions on Genero archive
(.gar) files on the GAS:
- list lists all deployed gar files.
- deploy deploys a gar file.
- undeploy undeploys a gar file.
- enable enables a gar file.
- disable disables a gar file.
- secure secures a gar file.
- unsecure unsecures a gar file.
- delegate configures delegation in a deployed Genero archive.
- config configures application security on the Identity Provider (IdP).
- options. Some options are specific to commands and these are described in the tables in DeployGar command options.
- args include the URL of the GAS. Some arguments are specific to commands and these are described in the next paragraphs.
Syntax 1: list archives
DeployGar list [ options ] url
- options are described in Table 1
- url is the GAS base URL
Syntax 2: deploy/enable/secure archives
DeployGar {
| deploy | undeploy
| enable | disable
| secure | unsecure } [ options ] archive url
- options are described in Table 1
- archive is the Genero archive file name
- url is the GAS base URL
Syntax 3: delegate
DeployGar delegate [ options ] archive xcf url
- options are described in Table 2
- archive is the Genero archive file name
- xcf is the file name of the application configuration file (.xcf) in the archive
- url is the GAS base URL
Syntax 4: config
DeployGar config [ options ] operation client_id url
- options are described in Table 3
- operation to perform security configuration on IdP must be one of the
following:
{ get | set }
- client_id is the OAuth client ID of the application
- url is the GAS base URL
DeployGar command options
Option | Description |
---|---|
|
Displays help for the command. |
|
Specifies the HTTP user name. |
|
Specifies the password of the HTTP user. |
-t, --token value
|
Specifies the access token value. |
-f, --tokenfile
filename
|
Specifies the access token file. |
-x, --xml |
Output result of command in XML format. |
Option | Description |
---|---|
|
Displays help for the command. |
|
Specifies the HTTP user name. |
|
Specifies the password of the HTTP user. |
-t, --token value
|
Specifies the access token value. |
-f, --tokenfile
filename
|
Specifies the access token file. |
Option | Description |
---|---|
|
Displays help for the command. |
|
Specifies the HTTP user name. |
|
Specifies the password of the HTTP user. |
-t, --token value
|
Specifies the access token value. |
-f, --tokenfile
filename
|
Specifies the access token file. |
-c, --config
filename |
Specifies the configuration file name. |
Usage
Use a command with the help option to display available options. For example:
DeployGar config --help
Some examples are given in the next paragraphs using DeployGar.
Get list of deployed gar files
Run this command to get a list of deployed gar files on a GAS. Mainly, you would use this to check your access is working; that you have an up-to-date access token, and that the GAS URL is reachable.
DeployGar list --xml --tokenfile mytoken.json
GAS_base_URL
- The
--xml
option is specified for the format of the output. - The
--tokenfile
option needs the path to a file name where the access token got from the IdP is saved. See GetToken for details of getting the access token. - GAS_base_URL is the URL for the Genero Application Server (GAS) where you
want to see a list of deployed
applications.
https://host:port/gas
Deploy a gar file
Run this command to deploy a Genero archive file.
DeployGar deploy -f mytoken.json myGarfile.gar
GAS_base_URL
- The
-f
option (short option for--tokenfile
) gives the path to a file name where the access token got from the IdP is saved. - GAS_base_URL is the URL for the Genero Application Server (GAS) where you
want to deploy the
application.
https://host:port/gas
For more examples, see Automate application deployment via scripts and Automate application configuration via scripts.