8000 fix: keep cluster edits atomic on invalid references by eddiethedean · Pull Request #75 · dmux/minilake · GitHub
[go: up one dir, main page]

Skip to content

fix: keep cluster edits atomic on invalid references - #75

Merged
dmux merged 2 commits into
dmux:mainfrom
eddiethedean:codex/fix-issue-49-cluster-edit-atomic
Oct 29, 2026
Merged

dmux merged 2 commits into
dmux:mainfrom
eddiethedean:codex/fix-issue-49-cluster-edit-atomic

Conversation

@eddiethedean
Copy link
Copy Markdown
Collaborator

Summary

  • Validate policy and instance-pool references before applying a cluster edit.
  • Build the proposed cluster response before mutating stored state.
  • Add regression coverage proving failed policy and pool edits preserve the complete cluster record.

Fixes #49

Validation

  • ruff check src/minilake/services/clusters.py tests/test_cluster_policies.py
  • pytest -q tests/test_cluster_policies.py (13 passed)

@eddiethedean
Copy link
Copy Markdown
Collaborator Author

Ready to merge. Review found no actionable issues. The fix addresses #49 by validating cluster edits before mutating stored state, with regression coverage confirming missing policy and pool references leave the complete cluster record unchanged.

Validation: all 22 cluster and policy tests passed locally, and CI lint, test, and UI checks passed.

@dmux dmux self-assigned this Oct 29, 2026
@dmux dmux added the bug Something isn't working label Oct 29, 2026
@dmux
dmux merged commit a40ddb1 into dmux:main Oct 29, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Cluster edits rejected for missing policy still change configuration

2 participants

0