In case when we deploy Cloud-Pipeline with basic IdP and additionally providing SSO_ENDPOINT_ID for services such as
api-srv
git
The deployment script would behave unexpectedly. Despite we specify ENDPOINT_ID explicitly it will still register these apps with default value like https://{external_host}:{external_port}/<context-path>
This changes modify this behaviour to use SSO_ENDPOINT_ID if provided, otherwise use default value
In case when we deploy Cloud-Pipeline with basic IdP and additionally providing SSO_ENDPOINT_ID for services such as
The deployment script would behave unexpectedly. Despite we specify ENDPOINT_ID explicitly it will still register these apps with default value like
https://{external_host}:{external_port}/<context-path>This changes modify this behaviour to use SSO_ENDPOINT_ID if provided, otherwise use default value