ContributionsMost RecentMost LikesSolutionsRe: SwaggerHub to Apigee integration whacks policies, etc. This is not supported. See the article: https://app.swaggerhub.com/help/integrations/apigee-edge?_ga=2.194677869.1701097291.1552423253-1907065053.1530279264 This is not a fully blown solution to integration. We would recommend it for creating a proxy initially but turn it off after that. For example, adding operationId or updating a description to an endpoint, are you wanting a whole new revision in Apigee? And run through re-creating policies and resources, even if it is cpoy/paste? Clearly the answer is NO if you are managing multiple APIs and incorporating CI/CD. Frankly disappointing. SwaggerHub to Apigee integration whacks policies, etc. When SwaggerHub to Apigee integration is executed it creates a new revision with the changes made updated as expected, but the new Revision once again has the default policies, and has blown away all our added policies and flows. Any workaround, or are we incorrectly using/applying the integration? Re: SwaggerHub Apigee Integration requires Target Endpoint... The way around this is to satisfy it with a virtual endpoint, eg., virtserver.swaggerhub.com SwaggerHub Apigee Integration requires Target Endpoint... We do not have a proxy target in our Apigee proxy and SwaggerHub integration with Apigee it is a required field. Is there a way around that? Also, the Target Endpoint field does not allow an IP address, eg., if it is proxying an internal service. Is there a way to work around this as well? Thanks!