TBI - Expose functionality to facilitate the creation of SAP BTP subaccount destinations during the CF discovery flow

[longieirl]

Description (include screenshots)

Currently, during the CF discovery flow on BAS, when you select an ABAP environment, it will show you the appropriate ABAP service to allow you to connect to your ABAP cloud instance.

When you select this ABAP environment system, it will generate a SAP BTP subaccount destination or update the existing destination using the following naming convention;

abap-cloud-<abap-environment-name-<cf-target-org>-<cf-target-space>

The SAP BTP destination is created using OAuth2UserTokenExchange and will append the appropriate UAA settings to allow connectivity to the backend.

The goal is to leverage the cf-tools to generate the destination as the flow is only required for BAS.

Existing flow;

For more information on this specific destination type;

https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/oauth-user-token-exchange-authentication

Value

• remove dependency on internal module
• more maintainable code

Architecture Elaboration

Notes

Tasks

• Expose new functionality from axios-extension module
• Leverage cf-tools and axios modules to validate and generate a new SAP BTP destination using the BAS H2O_URL proxy to call the create API endpoint