SAP
Html5 Repositiry binding destination?
On the command line I have these names for the destinations
In BTP I have these names
He is using BTP destination. It shouldn't be the same destination, in the beginning each application had its own service. Is there a way to force binding to the correct service?
@luizcarlospedrosogomes , thanks for reporting an issue!
In SAP BTP there are two different types of destinations:
- subaccount level destinations, shared across all applications and subscriptions within same BTP subaccount. There is no dedicated Destination service instance for this type of destination configurations. The lifecycle of these destination configurations is bound to BTP subaccount.
- instance level destinations, visible only to those CF applications that have access to credentials of Destination service instance, on level of which the destination configuration was defined. The lifecycle of these destination configurations is bound to specific Destination service instance (deletion of instance will delete all destination configurations attached to it, and leave all other destination configurations untouched).
The list of destination names in the BTP Cockpit HTML5 Applications shows destination names as they are defined in the Destination service instance level destinations.
The cf html5-list -d shows list of HTML5 applications as they exposed via subaccount level destinations. To see the list of HTML5 applications available via service instance level destination configurations, you can use cf html5-list -di <destination_service_instance_name>. Currently there is no command to see all HTML5 applications exposed by all service instance level destinations of all Destination service instances, so you will need to specify <destination_service_instance_name>.
As it looks now from the screenshots you attached, you have both subaccount and instance level destination configurations pointing to the same html5-apps-repo/app-host service instances. This is the source of the confusion. In most cases, you don't need both. So, if there is no specific scenario that requires to keep HTML5 destinations on the subaccount level (e.g. standalone AppRouters in different spaces that should serve same app-host HTML5 applications), but rather you consume HTML5 applications via SAP Portal / Workzone - you can delete subaccount level destinations to avoid confusion.
