how to promote proxy from from dev to higher environemnts using apigeetool

[nagasakethjalig]

I am a Release engineer in my company and planning to implement the CI/CD for api proxies.

For regular applications we use "Build once - Deploy many" concept.

i.e we just build the application once in dev job and push it to artifactory.

from QA-PROD jobs they get the latest version deployed to artifactory and deploy the same to the

corresponding environment.

I want to implement the same for api proxies.But the problem i am facing is am not seeing any command in apigetool to get the latest revision of a particular api proxy and also a way to promote the revision to deploy to higher environemnts.

can someone help me in this ?

[kurtkanaskie]

Hi @NAGA SAKETH JALIGAMA,

Unfortunately there is no command to list revisions in apigeetool.

You could use an Edge API call to see that:

$ curl -n "https://api.enterprise.apigee.com/v1/o/ORG_NAME/apis/features-v1"
{
  "metaData" : {
    "createdAt" : 1578428227628,
    "createdBy" : "defaultUser",
    "lastModifiedAt" : 1586525484869,
    "lastModifiedBy" : "defaultUser",
    "subType" : "null"
  },
  "name" : "features-v1",
  "revision" : [ "1", "2", "3", "4", "5" ]

However, you could merely deploy another revision of the proxy from artifactory using:

$ apigeetool deployProxy -N -o ORG_NAME -n features-v1 -i
"features-v1" Revision 5
  undeployed
  environment = undefined
  base path = undefined

Then use apigeetool commands `listdeployments` and `deployExistingRevision`.

NOTE: deployExistingRevision currently uses a hard coded value of 60 seconds for delay.