New "Promote" goal: deploy existing proxy revision to another environment

g-lalevee commented 1 year ago

To be able to keep the same revision number across several environment, it could be useful to be able to redeploy a proxy revision to another environment without having to rebuild it (and Apigee X creates a new revision number for each build...)

Scenario:

1- build proxy and deploy it to dev environment mvn install -Dorg=MyOrg -Denv=MyEnv ...

2- when proxy ok, promote a development revision to test environment. Options:

choose a version number to be deployed into target environment (if revision doesn't exist, error) mvn promote -Dorg=MyOrg -Denv=TargetEnv -Drevision=23 ...
choose the latest existing revision in the organization to be deployed into target environment mvn promote -Dorg=MyOrg -Denv=TargetEnv ...
choose the latest revision deployed in a given environment to be deployed into target environment mvn promote -Dorg=MyOrg -Dsource=SourceEnv -Denv=TargetEnv ...

g-lalevee commented 1 year ago

Addendum: promote goal should work with both Proxy and Shareflow

ssvaidyanathan commented 1 year ago

@g-lalevee - what if for

choose the latest revision deployed in a given environment to be deployed into target environment mvn promote -Dorg=MyOrg -Dsource=SourceEnv -Denv=TargetEnv ...

there are no revisions deployed in the sourceEnv? do we pick the latest revision in the org and deploy that or throw an error? I prefer throwing an error. But wanted to check with you

ssvaidyanathan commented 1 year ago

Released in v2.4.0

apigee / apigee-deploy-maven-plugin

New "Promote" goal: deploy existing proxy revision to another environment #204