I have a CI/CD pipeline in Azure DevOps where in the build pipeline I get the final proxy bundle exported using the Edge management API and stored as an artifact in a repo.
Then I use it in the Release pipeline to deploy it to the first environment. I tried to use the apigeetool to deploy the bundle, which deploys it as a new revision. But I need the latest revision on edge to be deployed, which is what I have in the artifact already.
Since earlier I was using the Edge management API, i didn't have an issue with the deployment
I have figured that the apigee deploy maven plugin can solve this issue of deploying the same revision.
Please note, i am deriving the proxyname from the swagger spec, and getting the latest revision of this proxy using scripts and exporting it out into a repo.
Also, at a later point, will be using this extracted artifact to deploy to different environments. Based on the branching -merging strategy posts on the community, I will go with different branches for different environments but I need to ensure code traceability and possibility of deploying the same revision to different environments as well.
My question is can I achieve the above with the apigee deploy maven plugin?
LinkedIn
Twitter
