Adding proxy metadata to check which version of proxy was deployed

[#1]

Hi,

We are planning auto generate proxies from swagger files and run nightly builds to deploy proxies generated from swagger. This process will first check if there is any change or not.

We want to stamp an internal version number or hash of swagger to an api proxy. We will use it to check if the new proxy being deployed is same as the one already deployed and make a decision to deploy or do nothing.

We could look at using description metadata tag but that is not being returned from a get api call.

Thanks,

Jaskaran

[ssvaidyanathan]

HI @jaskarangump

How are you converting the Open API (swagger) specs to proxies ? Which tool are you using ?

[#3]

We have written our own tool for our specific requirements. We also looked at https://github.com/anil614sagar/openapi2apigee

[ceber]

Why not use your vcs to drive that? When someone checks in a change to the specification, pull latest proxy definition, generate with your tool, then check in changes. If vcs indicates there are changes, deploy new revision of proxy?

[#5]

Thanks @Carlos Eberhardt. This works when we want to deploy on a commit. However, we also want to have a strategy to deploy nightly or weekly. And it would be nice for the build to ask the server if it has the latest or not.

[adas]

@jaskarangump first of all, Apigee would be coming up with a swagger spec to proxy wizard in the upcoming Unified UI, which is in beta right now. So you should try to leverage that as much as possible. Regarding the meta data linking, I think the @Carlos Eberhardt suggestion makes perfect sense.

[#7]

Hi @arghya das. Thanks for the info. UI would help for gettings started quickly. However not for automation.

Does the UI rely on openapi2apigee utility? One of the concerns we had with that is adding Apigee specific tags to swagger files, which makes it API manager specific.

[adas]

The UI is probably calling a combination of third party components and some in-house components to do the swagger to apiproxy conversion. But you are right, I don't think that would be exposed as a service that you can use as an API for your automation.