You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a considerable amount of global settings have empty strings as their default values. Therefore, when the resetConfiguration API is executed for these configurations, the value is restored to an empty string (default value), as expected.
However, another way to reset configuration values is by executing the updateConfiguration API, specifying the value parameter to an empty string. The current behavior of the API workflow is to update the configuration value to NULL in the database. To avoid bugs down the line in these scenarios, such as eventual NPEs, the API workflow should be modified to consider the configuration's default value.
Therefore, for instance, when executing the following API call:
Currently, a considerable amount of global settings have empty strings as their default values. Therefore, when the
resetConfiguration
API is executed for these configurations, the value is restored to an empty string (default value), as expected.However, another way to reset configuration values is by executing the
updateConfiguration
API, specifying thevalue
parameter to an empty string. The current behavior of the API workflow is to update the configuration value toNULL
in the database. To avoid bugs down the line in these scenarios, such as eventual NPEs, the API workflow should be modified to consider the configuration's default value.Therefore, for instance, when executing the following API call:
The
backup.plugin.veeam.password
configuration value should be changed to an empty string in the database, because its default value is notNULL
.Accordingly, for settings such as
api.allowed.source.cidr.list
, which has"0.0.0.0/0,::/0"
as default value, when executing the following API call:The setting's value stored in the database should be an empty string, and not
NULL
.The text was updated successfully, but these errors were encountered: