NOTEYou can use the
ssd api-management undeploy apicommand or its shortened versionssd apim undeploy api.
The ssd api-management undeploy api command must be followed by flags with their respective arguments:
If no flag is specified, the interactive mode will be activated.
You must specify the environment from which you want to undeploy the API and which revision will be undeployed. Example:
The following flags can be used with the ssd api-management undeploy api command:
Flag | Type | Description |
|---|---|---|
| -v, --api-version | string | Version of the API that will be undeployed |
| -e, --environment | string | Environment from which the API will be undeployed |
| -h, --help | Displays help for the command |
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 undeploy an API (i.e., from an environment) 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