Due to the issues raised in this discussion, it makes sense to allow the underlying property source to be modified or refreshed after it has already been initialized. Not allowing modification in the underlying source results in convoluted test setups, which can add both complexity and unnecessary execution time when requiring each test to run in a separate JVM in order to be able to change the underlying config source.
Simply giving public access to the DynamicProperty.updateProperty and DynamicProperty.updateAllProperties here should be sufficient.
Due to the issues raised in this discussion, it makes sense to allow the underlying property source to be modified or refreshed after it has already been initialized. Not allowing modification in the underlying source results in convoluted test setups, which can add both complexity and unnecessary execution time when requiring each test to run in a separate JVM in order to be able to change the underlying config source.
Simply giving
public
access to theDynamicProperty.updateProperty
andDynamicProperty.updateAllProperties
here should be sufficient.