NOTEYou can use the
ssd api-management update apicommand or its shortened versionssd apim update api.
The ssd api-management update api command can be followed by flags with their respective arguments:
If no flag is specified, the interactive mode will be activated.
See below an example of usage in the direct mode:
The following flags can be used with the ssd api-management update api command:
Flag | Type | Description |
|---|---|---|
| -d, --description | string | API Description |
| -h, --help | Displays help for the command | |
| -n, --name | string | New name for the API |
| --new-version | string | New value for the API version. If omitted, the value of the version field will remain the same |
| -p, --path | string | Base path of the API to be modified |
| --responsible-team | Team responsible for the API | |
| --responsible-user | User responsible (login) for the API | |
| -r, --revision | string | Revision of the API to be modified |
| -s, --stage | string | Workflow stage of the API to be modified |
| -t, --team | string | Name of the team if the API has the visibility type "TEAM" |
| -v, --version | string | Version of the API to be modified |
| --visibility-type | string | Visibility type of the API to be modified |
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 update a Rest 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