Accept case insensitive values in boolean settings #10663
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, when updating boolean settings, the Management Server performs a case sensitive validation of the inserted values. Thus, only the
true
andfalse
values are accepted.This PR proposes to extend this validation to encompass case insensitive boolean values. Therefore, values such as
True
andFALSE
will be accepted and will be properly normalized before being persisted in the database.Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Screenshots (if appropriate):
How Has This Been Tested?
quota.enable.service
global setting toFaLsE
.updateConfiguration
API executionPersisted configuration value in the database
TRUe
:updateConfiguration
API executionPersisted configuration value in the database