provide component provision status endpoint

[stitakis]

Currently when an component is being provisioned if no error happens a successful response is sent back to the client (front end or endpoint consumer).

However this successful answer just means that the provisioning app was able to process the request and triggered successfully the corresponding jenkins pipeline.

The whole provisioning process is asynchronous. The provisioning app just place a task in jenkins.

Endpoint consumers miss in this way to get the end result of the quickstarter jenkins pipeline.

To allow further orchestration of provisioning processes in a corporate environment a new endpoint is needed.

In this context, the provisioning app also need to provide an endpoint that could be used to return the status of the quickstarter jenkinsline.

A solution for this is to use the current provision app connection to openshift and query the result of the corresponding triggered pipeline.

[stitakis]

@metmajer @michaelsauter this enhancement needs to be implemented to satisfy the corporate needs

[michaelsauter]

Agree that this is a long-standing pain point.

An alternative to querying the pipeline would be to call an prov app endpoint from the pipeline when it is done. However, I think querying (as you suggest) is the better way because that should be more reliable in the face of errors.

That said, it tightens the prov app <-> OpenShift connection further, which has been introduced a bit ad-hoc and clear responsibilities have not been assigned yet. It would be good to further think about and clarify the role the prov app should play when it comes to OpenShift. Do you have something in mind where the boundaries should be?

[stitakis]

moved to ODS 4.1.0