Gateway Policy Plugin : creating versions for environment bundle's
search cancel

Gateway Policy Plugin : creating versions for environment bundle's

book

Article ID: 212372

calendar_today

Updated On:

Products

CA API Gateway

Issue/Introduction

When we add a policy version  to the "build" options the policy plugin is  creating  a policy bundle  with a version as expected but the environment bundle is also versioned for some objects like the JMS connector  ,

is there a way to prevent the environment bundle to be versioned as this is not desired in most cases. 

The JMS connector does not change and  we don't want to re-import environment variables  ! 

Environment

Release : 10.0

Component : API GATEWAY

Resolution

You can prevent the policy plugin to create version for the enviroment bundle by adding the following property  "com.ca.apim.build.disableEnvironmentEntityUniqueNaming=false" 

with the required prefix (i.e., systemProp) in gradle.properties file.

systemProp.com.ca.apim.build.disableEnvironmentEntityUniqueNaming=true

This will tell the plugin not to create versions for the environment bundle and the JMS endpoint should now look like :

type"JMS_ENDPOINT"
  name"JMS-connection"

instead off

type"JMS_ENDPOINT"
  name"::Policyname::JMS-connection::1.2.1"