TBI - Allow custom ABAP instances to be filtered during the CF discovery flow

[longieirl]

Description (include screenshots)

Currently, the CF discovery flow is dependent on the @sap/cf-tools to retrieve a list of ABAP instances based on a predefined and known list, for example;

open-ux-tools/packages/inquirer-common/src/prompts/cf-helper.ts

Line 19 in 3e0f5d4

const filteredInstances = [

During the CF flow, as shown below, the user might want to expose other types of ABAP instances that might not be defined using the predefined list as above;

In some instances, customers might want to expose other known service types. To support this, the CF discovery should allow additional service types to be added to the filtered list, for example;

Load from .env file;

ABAPEnvServiceTypes=internal,test

Load from shell;

ABAPEnvServiceTypes="internal,test" node app.js
# or pre-scripting your env variables
export ABAPEnvServiceTypes='internal,test"

Value

Provides an additional way to load ABAP instance types.

Architecture Elaboration

No

Notes

Tasks

• Read additional service types from process.env
• Add new unit tests