[JUJU-3505] AllWatcher additional attrs #15529
Merged
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.
In order to help with the dashboard UI and to remove redundant subsequent calls to the API server for the same data, we just expose more information from the AllWatcher.
The code turned out to be relatively simple, we just weren't exposing it. Although, I'm starting to believe the AllWatcher is an anti-pattern, by sending data with the changes, rather than just what's changed leading to a better query API. The downside with the AllWatcher is that the data being sent has to accommodate all the data and it very much feels like we're passing data via a back channel. The API itself would be better served with a better query API.
Checklist
QA steps
Apply the following diff:
$ juju bootstrap lxd test --build-agent $ juju add-model default $ juju wait-for model default
You should now see the new changes in the log from the model.
Bug reference
https://bugs.launchpad.net/juju/+bug/1939341