[
https://issues.apache.org/jira/browse/KARAF-7555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609533#comment-17609533
]
Matt Pavlovich commented on KARAF-7555:
---------------------------------------
Observability. How would users be aware if the value is actually set? Maybe a
config flag to allow it or an option flag on config:list and service:list to
show values?
If security is the reason, perhaps that could be masked? (ie "****" to show a
value is present)
Might be good to default:
1. Do not show env variable interpolation
2. Do not display OSGi "hidden" secret service values ("_secret field = secret
value")
3. Add option flag (perhaps limited by role) so admins have a way to view the
actual data for troubleshooting?
> config-list and service-list do not interpolate ${env:..} values
> ----------------------------------------------------------------
>
> Key: KARAF-7555
> URL: https://issues.apache.org/jira/browse/KARAF-7555
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.3.7
> Reporter: Matt Pavlovich
> Priority: Major
>
> When a config value is set to use an environment variable, config:list and
> service:list commands do not interpolate for ${env:FOO}
> For given config file:
> {noformat}
> bar = ${env:HOSTNAME}
> {noformat}
> {noformat}
> karaf@root()> config:list "(service.pid=org.foo)"
>
>
> ----------------------------------------------------------------
>
>
> Pid: org.foo
> BundleLocation: ?
> Properties:
> bar =
> felix.fileinstall.filename = file:/..../etc/org.foo.cfg
> service.pid = org.foo
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
