Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Review how to handle change / delete config properties
Description
There is some concern about changing property type / validation (e.g. change max, min, pattern). We currently do not handle such logic. We need to agree on some behaviour. May be add an option to force override invalid config when it change schema. Same as delete property. It will be painful if we fail to start opennms and customer need fix it in database.
Delete property
Config contain 3 property, we want to remove 1 of them.
Current:
If you delete property from schema. The changelog will fail due to config contain unknown property. (the one deleted in schema)
Expect:
Either remove or ignore the removed property.
Change property:
current config is 1000, we change schema max to 100. Or current config is 0 / 1, we change to boolean
Current:
In some case, changelog will be fail due to invalid existing value in config.
There is some concern about changing property type / validation (e.g. change max, min, pattern). We currently do not handle such logic. We need to agree on some behaviour. May be add an option to force override invalid config when it change schema. Same as delete property. It will be painful if we fail to start opennms and customer need fix it in database.
Delete property
Config contain 3 property, we want to remove 1 of them.
Current:
If you delete property from schema. The changelog will fail due to config contain unknown property. (the one deleted in schema)
Expect:
Either remove or ignore the removed property.
Change property:
current config is 1000, we change schema max to 100. Or current config is 0 / 1, we change to boolean
Current:
In some case, changelog will be fail due to invalid existing value in config.
Expect:
Besides schema, config should properly handled.