BUG - ABAP inquirer is not handling the default package name read from ATO settings

[longieirl]

Description

When consuming a destination defined using tenantType of CUSTOMER and the following ATO settings;

<?xml version="1.0" encoding="utf-8"?>
<ato:settings developmentPackage="TEST_YY1_DEFAULT" developmentPrefix="YY1_" isConfigured="true" isExtensibilityDevelopmentSystem="true" isManagedExtensibilityActive="false" isNotificationAllowed="true" isPrefixNamespace="false" isTransportRequestRequired="false" operationsType="C" sandboxPackage="TEST_YY1_DEFAULT" sandboxPrefix="YY9_" tenantRole="07" tenantType="CUSTOMER" transportationMode="COL" xmlns:ato="http://www.sap.com/adt/ato"/>

The ui5-deploy.yaml configuration is generated using;

        app:
          name: YY1_BPTEST0303
          package: $TMP
          transport: ''

The package property should be updated with TEST_YY1_DEFAULT as read from the ATO settings.

Steps to Reproduce

Steps to reproduce the behavior:

1. Generate a HTML5 using a destination configured with tenantType of customer and
2. Add deployment configuration

Expected results

ui5-deploy.yaml is generated with a package of TEST_YY1_DEFAULT which is the value read from the ATO settings developmentPackage.

Actual results

package is defaulting to $TMP

Screenshots

If applicable, add screenshots to help explain the problem.

Version/Components/Environment

Add any other context about the problem here
OS:

• Mac OS
• Windows
• Other

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue might have been missed during normal development/testing cycle}

How can we avoid this

{if we don’t want to see this type of issues anymore what we should do to prevent}