[jira] [Commented] (KARAF-1404) Cluster command 'cluster:config-proplist' only output edited properties

["Jürgen Kindler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KARAF-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13428115#comment-13428115 ] 

Jürgen Kindler commented on KARAF-1404:
---------------------------------------

So, the assumption is that the user should not be able to access cellar config files using cluster commands at all?

Because now I simply get an error message "No configuration PID found for group default" if org.apache.karaf.cellar.groups is in the outbound blacklist ... is that the intended behavior?

I understand that I cannot set this config using cellar commands when it's outbound blacklisted, but wonder why I cannot see it. The error messages - when seen together have some level of obscurity:
{noformat}
karaf@trun> cluster:config-proplist default org.apache.karaf.cellar.groups
No configuration PID found for group default
karaf@trun> cluster:config-propset default org.apache.karaf.cellar.groups default.features.repositories.sync false
Configuration PID org.apache.karaf.cellar.groups is blocked outbound
{noformat}

So the read access claims it's not there (which is not true), but the write access tells me that it's blocked for outbound (which is does not specifically express that it's not there ...)
                
> Cluster command 'cluster:config-proplist' only output edited properties
> -----------------------------------------------------------------------
>
>                 Key: KARAF-1404
>                 URL: https://issues.apache.org/jira/browse/KARAF-1404
>             Project: Karaf
>          Issue Type: Bug
>          Components: cellar-config
>    Affects Versions: cellar-2.2.3
>         Environment: Karaf-2.2.7-SNAPSHOT
>            Reporter: Xiaoli Ding
>            Assignee: Jean-Baptiste Onofré
>            Priority: Minor
>             Fix For: cellar-3.0.0, cellar-2.2.4
>
>
> 1.Start Karaf and install cellar
> 2.using default properties of org.apache.karaf.cellar.groups.cfg:
> {panel}
> default.config.whitelist.inbound=*
> default.config.whitelist.outbound=*
> default.config.blacklist.inbound=org.apache.cxf.dosgi.discovery.zookeeper.server,org.apache.karaf.cellar.groups,org.apache.karaf.cellar.instance,org.apache.karaf.cellar.node,org.apache.karaf.management,org.ops4j.pax.web,org.talend.esb.locator,org.apache.karaf.shell,org.talend.remote.jobserver.server
> default.config.blacklist.outbound=org.apache.cxf.dosgi.discovery.zookeeper.server,org.apache.karaf.cellar.groups,org.apache.karaf.cellar.instance,org.apache.karaf.cellar.node,org.apache.karaf.management,org.ops4j.pax.web,org.talend.esb.locator,org.apache.karaf.shell,org.talend.remote.jobserver.server
> default.config.sync=true
> default.features.whitelist.inbound=*
> default.features.whitelist.outbound=*
> default.features.blacklist.inbound=cellar,jetty,http,tesb-locator-client,tesb-sam-server,tesb-derby-starter
> default.features.blacklist.outbound=cellar,jetty,http,tesb-locator-client,tesb-sam-server,tesb-derby-starter
> default.features.sync=true
> default.features.repositories.sync=true
> {panel}
> 3.then i excute the following cluster commands
> {panel}
> karaf@trun> cluster:config-proplist default org.apache.karaf.cellar.groups
> Property list for configuration PID org.apache.karaf.cellar.groups for group default
> Key                                      Value
> {panel}
> can not output the properties of org.apache.karaf.cellar.groups
> 4.then excute:
> {panel}
> karaf@trun> cluster:config-propset default org.apache.karaf.cellar.groups default.features.repositories.sync false
> karaf@trun> cluster:config-proplist default org.apache.karaf.cellar.groups
> Property list for configuration PID org.apache.karaf.cellar.groups for group default
> Key                                      Value
> default.features.repositories.sync       false
> {panel}
> now only output the edited properties
> it is not my expectation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira