[
https://issues.apache.org/jira/browse/CLOUDSTACK-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823495#comment-13823495
]
ASF subversion and git services commented on CLOUDSTACK-4169:
-------------------------------------------------------------
Commit 52de0dc2cae33831cebb23ed4bb81d8368ed33de in branch refs/heads/4.3 from
[~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=52de0dc ]
CLOUDSTACK-4835: Update global configuration test cases failed in master
Changes made in update/list configuration API to use ConfigDepot
CLOUDSTACK-4169: Scoped configuraion parameters logic moved to ConfigDepot
CLOUDSTACK-5163: missing parameters in configuration table
> Move all of the config.java enums to ConfigKey
> ----------------------------------------------
>
> Key: CLOUDSTACK-4169
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4169
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Alex Huang
> Assignee: Harikrishna Patnala
> Fix For: Future
>
>
> I added a class called ConfigKey and ConfigValue to supplant the current
> Config.java. Config.java is an enum which makes it difficult for other
> plugins to introduce configuration parameters. This also consolidates the
> idea that config variables can be changed dynamically or has scoped. It
> should consolidate how to check for validity of the value.
> This way plugins can introduce their own configs without changing the core
> system. The goal has to be to eliminate Config.java entirely. The stated
> todos are written in ConfigDepotImpl.java.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
