You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/03/28 05:54:41 UTC
[jira] [Commented] (KARAF-4514) Add config:install command and
MBean
[ https://issues.apache.org/jira/browse/KARAF-4514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944585#comment-15944585 ]
ASF subversion and git services commented on KARAF-4514:
--------------------------------------------------------
Commit 9cf319f129410c9756d1453c8d6082167a4f372f in karaf's branch refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=9cf319f ]
[KARAF-4514] Add config:install command and MBean operation
> Add config:install command and MBean
> ------------------------------------
>
> Key: KARAF-4514
> URL: https://issues.apache.org/jira/browse/KARAF-4514
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-config, karaf-management, karaf-shell
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.9, 4.1.1
>
>
> It's possible to directly deploy a cfg file using the {{<configfile/>}} element of a feature.
> However, it's not possible to do the same directly in Karaf (providing the cfg URL). The only way is to actually create the config (config:property-set, etc).
> We will provide a {{config:install}} command with the cfg URL as argument to deploy directly in the {{karaf.etc}} folder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)