in a similar vein to an earlier question re Bamboo and Mulesoft cloudhub deployments (https://community.atlassian.com/t5/Bamboo-questions/Need-Deployment-Automation-support-for-Mulesoft-using-Bamboo/qaq-p/606019) i am trying to access more information about Bamboo / Mulesoft integration and understand how we can change our (once working) CI/CD deployment process.
we have build plans which used the `pom.xml` of the mulesoft/anypoint studio project to do a `mvn clean deploy` that both builds a mule artefact (a .zip deployment archive) and deploys it into our local artifactory repo.
previously, a subsequent bamboo deployment plan took the .zip artefact and invoked a script step that used a (now deprecated) cloudhub API/CLI to create/initialse/start the app on cloudhub.
because the API/CLI is now deprecated we are now being told (from Mulesoft) to use a mvn plugin in our pom.xml to add a new `mule:deploy` step to deploy the mule app to cloudhub.
the problem is the .zip deployment archive has no pom.xml (unlike the anypoint studio build project), so i am trying to understand, from a Bamboo PoV, how to automate deployments of mule apps to cloudhub.
