In the CI/CD flow it is hard to determine, whether the HTML5 application was already deployed or not. Also branching of commands is not desired and in some cases not possible. It would be beneficial to have an option for html5-push to create destination and app-host instance in case they are missing, but use existing otherwise.
Possible syntax may be
cf html5-push -d --consecutive
or
cf html5-push --managed
Use cases matrix
HTML5 application already deployed
Destination with same sap.cloud.service exists
Action
No
No
Create app-host service instance and destination
Yes
No
Redeploy application to existing app-host and create destination
No
Yes
Create app-host service instance and update destination with extra app-host-id
Description
In the CI/CD flow it is hard to determine, whether the HTML5 application was already deployed or not. Also branching of commands is not desired and in some cases not possible. It would be beneficial to have an option for
html5-pushto create destination and app-host instance in case they are missing, but use existing otherwise.Possible syntax may be
or
Use cases matrix
sap.cloud.serviceexistsapp-hostservice instance and destinationapp-hostand create destinationapp-hostservice instance and update destination with extraapp-host-idapp-hostQualities of Change