NOTEYou can use the
ssd api-management deploy apicommand or its shortened versionssd apim deploy api.
The ssd api-management deploy api command can be followed by flags with their respective arguments:
If no flag is specified, the interactive mode will be activated.
You need to specify the environment to which you want to deploy the API and which revision will be deployed. Example:
The following flags can be used with the ssd api-management deploy api command:
Flag | Type | Description |
|---|---|---|
| -v, --api-version | string | Version of the API to be deployed |
| -e, --environment | string | Environment to which the API will be deployed |
| -h, --help | Displays help for the command | |
| -r, --revision | int | Specifies the revision of the API to be deployed |
Flag | Type | Description |
|---|---|---|
| -c, --config | string | Configuration file (default: $HOME/.sensedia/config.json) |
| --profile | string | The configuration profile you want to use (default: "default") |
| --verbose | Lists all requests made by the command. It is possible to store this information in a TXT file instead of displaying it on the terminal. E.g.: $ ssd (api-management | apim) list apis --verbose 2> log.txt |
NOTEIt is possible to deploy an API using a
.yamlfile with the declarative mode. Learn more.
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more