This is an automated email from the ASF dual-hosted git repository.
DaanHoogland pushed a change to branch ghi10752-config-core-4
in repository https://gitbox.apache.org/repos/asf/cloudstack.git
discard 8c44edf78ac use ConfigKeys for deployment planning, ELB, API rate
limit, LB and firewall settings
discard 31a9df6e81d fix the publish.resource.state.events description
discard 5bdb2a2cb6b use ConfigKeys for network, stats collector, storage, user
VM and account manager settings
discard 1803736cfd0 use ConfigKeys for ManagementServer, agent, secondary
storage and router settings
discard ee7248df1de use the renamed NetworkLBHaproxyStatsVisibility key
discard 8844036e82b read usage alert settings from the DB, not
ConfigKey.value()
discard e7adf4dae29 remove a null check that can never be true
discard 6e2554a84cb use ConfigKeys for alert, storage, guest network and
hidden settings
omit c800b9071eb fix config descriptions and the
NetworkLBHaproxyStatsVisibility name
omit 59dcb11f8d1 declare and register ConfigKeys for all remaining Config
enum entries
add 4dae995455e Improve Inherited Context Lookup in getConfigResources
(#11048)
add 5abbd02930a declare and register ConfigKeys for all remaining Config
enum entries
add 1a6e967834d fix config descriptions and the
NetworkLBHaproxyStatsVisibility name
add b1e495ea4e7 use ConfigKeys for alert, storage, guest network and
hidden settings
add 7958e471a59 remove a null check that can never be true
add 0caa968db29 read usage alert settings from the DB, not
ConfigKey.value()
add 3664fd48be6 use the renamed NetworkLBHaproxyStatsVisibility key
add 149bbda6aaa use ConfigKeys for ManagementServer, agent, secondary
storage and router settings
add 17957735c1b use ConfigKeys for network, stats collector, storage, user
VM and account manager settings
add f0a376cdf51 fix the publish.resource.state.events description
add f1571dda6b4 use ConfigKeys for deployment planning, ELB, API rate
limit, LB and firewall settings
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (8c44edf78ac)
\
N -- N -- N refs/heads/ghi10752-config-core-4 (f1571dda6b4)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../model/impl/DefaultModuleDefinitionSet.java | 38 +++++++++++++++-------
1 file changed, 27 insertions(+), 11 deletions(-)
