Installation of proxy

[#1]

Hi Everyone,

I need clarification on deploying proxy to higher environments(E2 & E3). We are in initial stage of deploying proxies in our organization. We may need to add flows in already deployed proxy in future. We follow different regions for promoting code. E3 is production region & E2,E1 are test region. If i want to add new flow in existing E3 proxy how should i proceed. Is following approach correct,

1. Take export of proxy from E3.

2. Import it in development region.

3. Add changes on top of it.

4. Promote proxy to E2 & then to E3.

Let me know if there is better way to achieve this.

Thanks,

Roshan.

[guy_hagemans]

So I understand you have a seperate organization deployed for the use of 'environments'? On the one hand that's strange, because within one Edge 'organization' you should be able to set the 'dev', 'test' and 'prod' environments (or more in a on-premise deployment.).

Anyway, if you can't simply promote the proxy using the Edge UI, exporting and importing is probably the best way. You could maybe also use the apigeetool for that. see:

https://www.npmjs.com/package/apigeetool

using 'fetchproxy' and 'deployproxy' this could go a lot faster by scripting it. Include it in a Grunt script to automatically save the revision to Github or so could also be useful. See:

http://docs.apigee.com/api-services/content/deploy-api-proxies-using-management-api#scriptingagainst...

Also, when deploying to production, you might want to check the API to deploy using the 'override' command. See the APIgee documentation for that, as it enables 'zero downtime' (or seamless) deployment

see: http://docs.apigee.com/api-services/content/deploy-api-proxies-using-management-api#seamless