feat: publication for blueprint upgrade status SOFIE-2258 #1049
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.
feature
When viewing the upgrades/migrations page in the ui, it calls a method to fetch the status, with a button to refresh the data.
When the
/health
endpoint is called, it will perform the same calculations with no caching between calls.This status calculation has been moved into a custom publication. This helps simplify the frontend code, avoiding the need for the method call and refresh button handling, and also makes the data much more reactive as it is changed.
The systemStatus (
/health
) endpoint uses this same publication, adding a handle to the publication on first call of the endpoint, and keeping the handle until sofie exits.This was motivated by wanting to add the upgrade buttons to the blueprint config pages, to make it easier to run the upgrades (which you should be doing after making any config changes) and to see that they need running when editing the config. (this likely needs some thought on styling)
Status