Custom parameters to be passed on XaaS blueprints response

[Gaurav_Sangamne]

Hi All,

I have a requirement, I have a client with vRA 7.2 env where XaaS blueprints are defined with multiple base blueprints inside. For e.g. an XaaS blueprint has a base blueprint to provision VM, another blueprint to conduct tasks like opening a ITSM ticket etc. The XaaS blueprints are triggered via an external system.

This external system needs to receive response of VMs provisioned via base blueprints. Now, Since the external system is calling XaaS blueprint, it has no clue of base blueprints.

My question is, is there a way if I can modify the API response of XaaS blueprint and append additional parameters to incorporate data of base blueprints ? For e.g. I want to modify the XaaS blueprint API response to also contain the request ID number of base blueprint ?

Appreciate the help and expertise ..

Thanks

[NuggetGTR]

I am assuming you are hitting the vRA API directly to call the XaaS?

Have you thought about hitting vRO API from the external system calling the exact same XaaS workflow? You can then control what you want to output like the request number of the additional base deployment. vRA API return is limited specially if your wanting details like the request number of a sub deployment which in turn is another API request separate from your original

[Gaurav_Sangamne]

Hello NuggetGTR,

Thanks for your response. You are right, I have the constraint of hitting the vRA API only due to network restrictions... I can't hit the vRO APIs directly. Moreover vRA will have the XaaS blueprint and the corresponding child blueprints, it will be tedious to call all individual child blueprints on vRO directly in an orchestrated manner..

Its a good suggestion though, I will explore this more.

Thanks

[NuggetGTR]

I am assuming you are using an external vRO then? if the internal vRO is being used the same address would be hit for both vRA and vRO API which would remove the network restriction.

Considering the XaaS blueprint is a vRO workflow it hopefully shouldn't be too hard to make some small changes to allow for the return of the child blueprints information as part of that workflow.

Cheers