Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat!(containers): deployment caching #816

Open
wants to merge 1 commit into
base: feature/application-management
Choose a base branch
from

Conversation

lusergit
Copy link
Collaborator

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 into state (to use the same naming schema as the other caching layers, see #812 #813 #814 and #815) and introduces a new resources_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.

@lusergit lusergit force-pushed the feat/deployment-caching branch from 6c32e43 to 333070b Compare February 10, 2025 14:18
@lusergit lusergit force-pushed the feat/deployment-caching branch 2 times, most recently from 898f85d to b985ba8 Compare February 13, 2025 11:34
- Decouples the deployment state (created, sent, stopped, stopping, ...)
  and the underlying resources states (created images, created networks,
  ...) from each other.
- The deployment state gets updated when the device publishes on the
  appropriate interfaces. Its state is cached and persisted in the DB so
  we dont have to query the device every time we want to update the
  deployment resources state.

Signed-off-by: Luca Zaninotto <luca.zaninotto@secomind.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants