Skip to content

MS: Persistent Executions Data#736

Draft
jjoderis wants to merge 36 commits intomainfrom
ms/deployment-information-persistence
Draft

MS: Persistent Executions Data#736
jjoderis wants to merge 36 commits intomainfrom
ms/deployment-information-persistence

Conversation

@jjoderis
Copy link
Copy Markdown
Contributor

Summary

Executions data is now persistently stored in the Management System to ensure that it is available when engine are not available or when a deployment has been removed from an engine.

Details

  • TODO

jjoderis added 30 commits March 31, 2026 09:03
…s/proceed into ms/deployment-information-persistence
…ept for future audit trail reference outside the spaces folder structure
…nown to the MS when some exist on an engine that has known deployments
…nstance in the MS so they can be accessed even if the engine goes offline or if the instance is deleted on the engine
…ason there is no way for it to be set back to being available
…reated empty which can lead to errors when the engine tries to read the file after restarting
… with a timer event leads to the deployment being activated and spawning processes before the engine is started completely
@github-actions

This comment has been minimized.

…ng and the activation of the instance recovery feature
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 7, 2026

CLOUDRUN ACTIONS

✅ Successfully created Preview Deployment.

https://pr-736---ms-server-staging-c4f6qdpj7q-ew.a.run.app

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.

1 participant