Skip to content

One best-effort reconcile policy for automatic setup triggers - #176

Merged
udaychandra merged 1 commit into
mainfrom
refactor/one-reconcile-wrapper
Jul 28, 2026
Merged

One best-effort reconcile policy for automatic setup triggers#176
udaychandra merged 1 commit into
mainfrom
refactor/one-reconcile-wrapper

Conversation

@udaychandra

Copy link
Copy Markdown
Contributor

Follow-up to #175 (review feedback): sail up and the boot sweep each carried an identical try-ensureInstalled-warn wrapper — two homes for one policy. The single-container best-effort reconcile now lives once in ContainerSetupSweep.reconcile; the sweep loops it, sail up calls it. Explicit-outcome callers (dispatch, provisioner, renamer, reconfigure) keep using ContainerSailSetup.ensureInstalled directly, which stays the one idempotent seam.

No behavior change; tests moved to the consolidated seam. mvn clean test green.

sail up and the boot sweep each carried an identical try-ensureInstalled-
warn wrapper. The single-container policy now lives once, in
ContainerSetupSweep.reconcile; the sweep loops it and sail up calls it.
Callers needing the outcome or their own error handling (dispatch,
provisioner, renamer, reconfigure) keep calling ensureInstalled directly.
@udaychandra
udaychandra merged commit 0df83f1 into main Jul 28, 2026
3 checks passed
@udaychandra
udaychandra deleted the refactor/one-reconcile-wrapper branch July 28, 2026 21:26
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