NOTEYou can use the
ssd api-management remove (plan | api)-interceptorcommand or its shortened versionssd apim remove (plan | api)-interceptor.
The ssd api-management remove (plan | api)-interceptor command can be followed by flags with their corresponding arguments:
If no flag is specified, the interactive mode will be activated.
Below you will find a usage example:
The following flags can be used with the ssd (api-management | apim) remove (plan | api)-interceptor command:
Flag | Type | Description |
|---|---|---|
| Flags for APIs | ||
| -n, --api-name | string | API name from which the interceptor will be removed |
| -s, --revision | string | API revision from which the interceptor will be removed |
| -v, --api-version | string | API version from which the interceptor will be removed |
| Flags for plans | ||
| -n, --plan-name | string | Plan name from which the interceptor will be removed |
| Other flags | ||
| -f, --flow | string | API or plan flow from which the interceptor will be removed (INBOUND or OUTBOUND) |
| -h, --help | Displays help for the command | |
| -m, --method | string | Method (operation) from which the interceptor will be removed (Optional). E.g.: POST |
| -a, --path | string | Operation path from which the interceptor will be removed (Optional). E.g.: /users |
| -p, --position | int | Position of the interceptor in the API or plan flow |
| -r, --resource | string | Resource name from which the interceptor will be removed (Optional) |
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 |
We use cookies to enhance your experience on our site. By continuing to browse, you agree to our use of cookies.Learn more