Apigee - Multiple Revisions deployed in same environment - Is it a bug ?

[anilsr]

Hello Apigeeks,

I can able to deploy multiple revisions of same API Proxy in same environment using Mgmt API. Is it a bug in the system ? I believe we can deploy only one revision of API Proxy in same environment. Please find attached image which shows both deployments are successful and deployment details API which confirms same.

{
  "environment": [
    {
      "name": "test",
      "revision": [
        {
          "configuration": {
            "basePath": "/",
            "steps": []
          },
          "name": "2",
          "server": [
            {
              "status": "deployed",
              "type": [
                "message-processor"
              ],
              "uUID": "2db95e89-fd44-4996-bea5-aee8a0eba302"
            },
            {
              "status": "deployed",
              "type": [
                "message-processor"
              ],
              "uUID": "ac5a9575-64a7-40c9-ab23-2c774cbfc7fb"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "998bdf1e-b8d0-4204-84d7-1e295526ad8c"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "5fc31fad-9b87-4168-824a-9f5e6beb5ce0"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "bcf41dfd-2810-4cfc-b23f-5427cba932fa"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "65cd0a4d-d09f-4b2d-a02a-3b14ccdf5386"
            }
          ],
          "state": "deployed"
        },
        {
          "configuration": {
            "basePath": "/",
            "steps": []
          },
          "name": "1",
          "server": [
            {
              "status": "deployed",
              "type": [
                "message-processor"
              ],
              "uUID": "2db95e89-fd44-4996-bea5-aee8a0eba302"
            },
            {
              "status": "deployed",
              "type": [
                "message-processor"
              ],
              "uUID": "ac5a9575-64a7-40c9-ab23-2c774cbfc7fb"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "998bdf1e-b8d0-4204-84d7-1e295526ad8c"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "5fc31fad-9b87-4168-824a-9f5e6beb5ce0"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "bcf41dfd-2810-4cfc-b23f-5427cba932fa"
            },
            {
              "status": "deployed",
              "type": [
                "router"
              ],
              "uUID": "65cd0a4d-d09f-4b2d-a02a-3b14ccdf5386"
            }
          ],
          "state": "deployed"
        }
      ]
    }
  ],
  "name": "cf-my-api.bosh-lite.com",
  "organization": "asagarnodeapp"
}

How does it work ? Is it a bug / my thinking is wrong ?

[#2 · Accepted solution]

@Anil Sagar API's revisions has different basepath, so it's expected to be deployed.

[anilsr]

Thank you @tskumar@apigee.com , You are right. It was due to different basepath.

[#4]

Hi @Anil Sagar, one reason for this to happen is to support seamless deployment or zero downtime. So, essentially, the new revision gets deployed while the first one drains any requests in flight. I wonder if you accidentally set override and delay parameters in the request. For more info checkout this page about seamless deployment. You may find some clues. http://docs.apigee.com/api-services/content/deploy-api-proxies-using-management-api

Hope it helps

[anilsr]

Thanks @Diego Zuluaga , It was due to different basepath.

[nagashree_b]

@Anil Sagar what is the best practice when you have different backends and base paths while the proxy code remains same?

should you have a new proxy with a new base path or deploy the same proxy as two different revisions for the different base paths

[DChiesa]

Hi -

Please do not ask new questions in "ANSWERS" to existing questions.

If you have a new question, use the "Ask a Question" button. If appropriate, you can cite the URL link for an existing question, in your new question.

Thanks!