AnsweredAssumed Answered

Templatized Value for a Context Variable

Question asked by acalbazana on Apr 7, 2016
Latest reply on Aug 29, 2016 by mtrinath

Hello,

Does anyone have a good way to templatize values for a context variable?

 

I currently use the GMU to export policy and then use the templatize feature to property drive certain values.  This works out okay. However, I noticed that when policy changes, the name of the properties also change.  This throws off my template scheme a bit.

 

Here is an example... I could have a policy template property start out as:

 

template.service.foo.Resources.ResourceSet.xml.All.OneOrMore.HttpRoutingAssertion.HttpRoutingAssertion.ProtectedServiceUrl.stringValue=http://dev.foo.com

 

Then later, I might add additional logic with an "At least one" or "All" assertions, which changes the template property name to something like this:

 

template.service.foo.Resources.ResourceSet.xml.All.OneOrMore.Required.All.Required.HttpRoutingAssertion.HttpRoutingAssertion.ProtectedServiceUrl.stringValue

 

Additional segments are being added to qualify the property.  This breaks my templating approach since I then need to figure out what has been modified and adjust accordingly.

 

What I'd like to do instead is define context variables up front thereby reducing the likelihood that they will change.  However, I do not see a way to "templatize" their value in the same way as what I've described above.  I know that I could get close to what I need with cluster-wide properties for this.  However, I don't like that approach as I will have several services to deal with.

 

Thanks,

 

Alejandro

Outcomes