feat!(containers): deployment caching #816
Open
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.
Currently deployments are hand-checked each time a device trigger is called. This PR decouples the state of the deployment and the state of the underlying resources and caches the deployment state sent by the device.
This change is breaking as it renames the old
status
attribute of a deployment intostate
(to use the same naming schema as the other caching layers, see #812 #813 #814 and #815) and introduces a newresources_state
attribute to signal the fronted the state of the underlying resources related to the deployment. If this PR gets merged the frontend should be upgraded as well.