Skip to content

feat(engine): close an engine on every node after its smss secrets change - #464

Merged
themaherkhalil merged 1 commit into
devfrom
feat/engine-clone-restart
Oct 26, 2026
Merged

themaherkhalil merged 1 commit into
devfrom
feat/engine-clone-restart

Conversation

@themaherkhalil

Copy link
Copy Markdown
Collaborator
  • When updateSmssFile saves an engine's settings to the secret store, it publishes the engine close to the cluster after reopening it locally, so every container reopens it with the new settings.

…ange

- When updateSmssFile saves an engine's settings to the secret store, it
  publishes the engine close to the cluster after reopening it locally, so
  every container reopens it with the new settings.
@themaherkhalil
themaherkhalil requested a review from a team as a code owner October 26, 2026 21:08
@snyk-io

snyk-io Bot commented Oct 26, 2026

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@themaherkhalil
themaherkhalil merged commit 19d68b8 into dev Oct 26, 2026
6 checks passed
@themaherkhalil
themaherkhalil deleted the feat/engine-clone-restart branch October 26, 2026 21:17
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