We should add a Feature to the mule-deploy-library that can create contracts between our published application and any applications it may need to call. This should be managed in a stand-alone (not attached to a deployment plane such as cloudHubDeployment) block that looks like the following:
We should discuss if clientApplicationName will automatically receive an environment specific suffix or will need to be passed with the appropriate suffix (such as using string interpolation to populate the environment).
@TimGonz-AVIO has already done some work around this, he can get you a copy of a customer fork of this repo that has the code he wrote to accomplish this task.
We should add a Feature to the mule-deploy-library that can create contracts between our published application and any applications it may need to call. This should be managed in a stand-alone (not attached to a deployment plane such as cloudHubDeployment) block that looks like the following:
We should discuss if clientApplicationName will automatically receive an environment specific suffix or will need to be passed with the appropriate suffix (such as using string interpolation to populate the environment).
@TimGonz-AVIO has already done some work around this, he can get you a copy of a customer fork of this repo that has the code he wrote to accomplish this task.