Details
-
Type:
Feature Request
-
Status:
Resolved
(View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 8.0.0.Alpha1
-
Component/s: Domain Management
-
Security Level: Public (Everyone can see)
-
Labels:
-
Git Pull Request:
-
Bugzilla References:
-
Similar Issues:
Description
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.
Issue Links
- relates to
-
WFLY-2795
Escaped expressions are still expanded at runtime
-
Activity
Brian Stansberry <brian.stansberry@redhat.com> changed the Status of bug 960820 from POST to MODIFIED
Paul Gier <pgier@redhat.com> changed the Status of bug 960820 from MODIFIED to ON_QA
Martin Simka <msimka@redhat.com> made a comment on bug 960820
verified on EAP 6.2.0.ER1
Martin Simka <msimka@redhat.com> changed the Status of bug 960820 from ON_QA to VERIFIED
mark yarborough <myarboro@redhat.com> changed the Status of bug 960820 from VERIFIED to CLOSED
[1:37pm] jsightler: well, yeah... but what if one of the ${} that is resolved is just a really weird password?
[1:39pm] bstansberry: jsightler: simple enough would be to add a "fail on non-resolvable" param to the recursive method and set it to true on the entry point and false when recursing