[
https://issues.jboss.org/browse/AS7-6964?page=com.atlassian.jira.plugin.s...
]
Jess Sightler commented on AS7-6964:
------------------------------------
I have added an initial pass at an implementation (with the above feature missing) in
order to solicit some feedback.
Basically, variable resolution happens in two places:
- The model node itself (System Property and Environment Variable resolution)
- The ExpressionResolver (vault)
I have worked around this by moving the call to node.resolve() into the
resolveExpressionsRecursively itself for the moment. I don't really see a way around
this with the current design, but it doesn't seem ideal to me.
Suggestions?
Recursive expression resolution
-------------------------------
Key: AS7-6964
URL:
https://issues.jboss.org/browse/AS7-6964
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Jess Sightler
When resolving an expression, keep resolving until the output of the resolution matches
the input.
Use case:
${sys.prop.with.host.specific.value}
resolves to
${VAULT::xxxxx}
which resolves to
thesecret
Basically, the main mechanism for customizing domain-level configs on a per-host basis is
to use expressions and use different values on each host. But this breaks down when a
vault expression is added to the mix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira