Here's what he said:
first, a `Configurations` record is added with the change and marked as active in the database. then, and the following process happens as many times as there are nodes in the cluster:
1. a record is added and marked active with the change and also this additional content added to the config data:
2. a record is added and marked active with the change and without the `FeatureFlags` data
Issue created from a message in Mattermost.
Make sure the reported issue doesn't reproduce anymore.
A smoke test around general functioning of the application, especially aimed at config changes.
To replicate, set up a Mattermost cluster with config in database and run the attached script. If you time it right you should see something like the attached screenshot.
I tested the app functionality and config changes in the sys console on prev.test set to v5.31.1-rc1 and did not find any issues.
Tested and passed against v5.31.1-rc1 and master. Configurations table only changes as expected and no unexpected additional row both in on-prem and cloud. Will take a look again once v5.32.0-rc2 becomes available.
Tested and passed on 5.32.0-rc2