Add dualwritehack worker that handles model concerns that need dual writing. #17347
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.
This is a hack. A horrible hack. But it allows us to isolate dual writing concerns to a single model worker that has access to both the model servicefactory and state. That can be deleted when the time comes that we have no mongo.
This is an eventually consistent approach to dual writing.
First example is dual writing model config. It watches model config, and smashes the values into state. Simple.
QA steps
juju.worker.dualwritehack updated model config in mongo
is in the logs.Documentation changes
Need to add this to the risk registry.
Links
Jira card: JUJU-