[
https://issues.jboss.org/browse/WFLY-1177?page=com.atlassian.jira.plugin....
]
John Mazzitelli commented on WFLY-1177:
---------------------------------------
Just wanted to make sure this fix includes my use-case where a sysprop value itself has an
expression in it for ssl config settings.
ca-certificate-file and certificate-key-file attributes on ssl=configuration resource - if
you set one of those to:
${x}
and x is a system prop whose actual value has an expression in it such as:
${jboss.server.config.dir}/my.keystore
we need it resolved fully for the web connector to start properly.
Recursive expression resolution
-------------------------------
Key: WFLY-1177
URL:
https://issues.jboss.org/browse/WFLY-1177
Project: WildFly
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