Log Interceptor Addition (ssd api-management add (plan | api)-interceptor log)

The ssd api-management add (plan | api)-interceptor log command allows you to add a "Log" interceptor to an API or plan flow on Sensedia API Platform.

You can use the ssd api-management add (plan | api)-interceptor log command or its shortened version ssd apim add (plan | api)-interceptor log.

Usage

The ssd api-management add (plan | api)-interceptor log command can be followed by flags with their corresponding arguments:

ssd api-management add (plan | api)-interceptor log [flags]

If no flag is specified, the interactive mode will be activated.

Below you will find usage examples in the direct mode:

# Adds a "Log" interceptor to the API or plan Inbound flow for all of its resources and methods
$ ssd (api-management | apim) add api-interceptor log --api-name "Open Banking" --api-version "1.0.0" --revision 1 --flow INBOUND
$ ssd (api-management | apim) add plan-interceptor log --plan-name "Plan Name" --flow INBOUND

# Use the flags `--encrypt-content` and `--encrypt-params` to encrypt the log contents and path/query parameters in the URL
$ ssd (api-management | apim) add api-interceptor log --api-name "Open Banking" --api-version "1.0.0" --revision 1 --flow INBOUND --encrypt-content --encrypt-params
$ ssd (api-management | apim) add plan-interceptor log --plan-name "Plan Name" --flow INBOUND --encrypt-content --encrypt-params

# Use the -y flag to skip the confirmation step about sensitive information
$ ssd (api-management | apim) add api-interceptor log --api-name "Open Banking" --api-version "1.0.0" --revision 1 --flow INBOUND --encrypt-content --encrypt-params -y
$ ssd (api-management | apim) add plan-interceptor log --plan-name "Plan Name" --flow INBOUND --encrypt-content --encrypt-params -y

# Adds an "Oauth" interceptor interactively
$ ssd (api-management | apim) add api-interceptor log
$ ssd (api-management | apim) add plan-interceptor log

Available Flags

The following flags can be used with the ssd (api-management | apim) add (plan | api)-interceptor log command:

Flag

Type

Description

Flags for APIs

-n, --api-name

string

API name to which the interceptor will be added

-s, --revision

string

API revision to which the interceptor will be added

-v, --api-version

string

API version to which the interceptor will be added

Flags for plans

-n, --plan-name

string

Plan name to which the interceptor will be added

Other flags

--encrypt-content

Encrypts content

--encrypt-params

Encrypts the path/query parameters contained in the URL

-f, --flow

string

API or plan flow to which the interceptor will be added (INBOUND or OUTBOUND)

-h, --help

Displays help for the command

-m, --method

string

Method (operation) to which the interceptor will be added (Optional). E.g.: POST

-a, --path

string

Operation path to which the interceptor will be added (Optional). E.g.: /users

-p, --position

int

Position of the interceptor in the API or plan flow

-r, --resource

string

Resource name to which the interceptor will be added (Optional)

-y, --yes

Skips the confirmation step

Global Flags

Flag Type Description

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`

-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

Thanks for your feedback!

EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]