-[Update and offboarding process](#update_invoker-and-offboard_and_deregister_invoker--invoker_capif_connector_updatepy-and-invoker_capif_connector_offboardingpy)
-[Onboard process](#onboarding-process)
-[Discover process](#discover-process)
-[Get JWT tokens](#obtain-invoker-tokens)
-[Update and offboarding process](#update-and-offboard-invoker)
-[Other Features](#other-features)
-[Register and Login](#script-register_and_loginpy)
-[Deregister and Login](#script-deregister_and_loginpy)
@@ -45,7 +45,7 @@ As explained before, OpenCAPIF SDK is designed to play two different roles:
CAPIF SDK allows developers to quickly implement NetApp provider flow in just some code lines. This section contains the full guide of all available features in SDK related to CAPIF providers.
## Important information for Providers
### Important information for Providers
Within the `provider_folder`, the SDK will store some folders named with the provided `capif_username` it has been previously registered from CAPIF administrator. At each folder, there will be found the following files:
@@ -156,7 +156,7 @@ For using this features we must be previously onboarded as a provider.
CAPIF SDK allows developers to quickly implement NetApp invokers flow in just some code lines. This section contains the full guide of all available features in SDK related to CAPIF invokers.
## Important information for Invokers
### Important information for Invokers
Within the `invoker_folder`, the SDK will store some folders named with the provided `capif_username` it has been previously registered from CAPIF administrator. At each folder, there will be found the following files:
@@ -166,7 +166,7 @@ Within the `invoker_folder`, the SDK will store some folders named with the prov
2. If it has already used the Service Discovery Functionality, it will be found all the available APIs with their information,
3. If it has already used the Service Get Token functionality, it will be found the access token for using the APIs that has already been discovered.