Change vmsnapshot.max
configuration to be dynamic
#9883
+6
−11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently, the configuration
vmsnapshot.max
isn't dynamic, and it is necessary to restart the Management Server after changing the configuration's value.This PR intends to change the
vmsnapshot.max
config to the newConfigKey
standard for dynamic configurations.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
To validate the changes, I performed the following steps without restarting the Management Server:
vmsnapshot.max
value to 2;vmsnapshot.max
value to 3;