Skip to content

fix: Record per cluster Classifier removal in the ClassifierReport - #529

Merged
gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:cleanup
Oct 30, 2026
Merged

gianlucam76 merged 1 commit into
projectsveltos:mainfrom
gianlucam76:cleanup

Conversation

@gianlucam76

Copy link
Copy Markdown
Member

undeployClassifier needed the cleanup of every cluster to complete within a single reconcile pass. Deployer results are consumed on read and, in pull mode, the ConfigurationGroup is deleted once the removal completes (a missing ConfigurationGroup is then treated as an error and a new Remove one is created), so with many Classifiers deleted at once the cleanup never converged.

When a Classifier is removed from a cluster, set the DeploymentStatus of the ClassifierReport to Removed. Reports already in that state are skipped on the next pass. removeClassifier now returns whether the Classifier was removed.

undeployClassifier needed the cleanup of every cluster to complete within a
single reconcile pass. Deployer results are consumed on read and, in pull mode,
the ConfigurationGroup is deleted once the removal completes (a missing
ConfigurationGroup is then treated as an error and a new Remove one is created),
so with many Classifiers deleted at once the cleanup never converged.

When a Classifier is removed from a cluster, set the DeploymentStatus of the
ClassifierReport to Removed. Reports already in that state are skipped on the
next pass. removeClassifier now returns whether the Classifier was removed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@gianlucam76
gianlucam76 merged commit bb83ec0 into projectsveltos:main Oct 30, 2026
9 checks passed
@gianlucam76
gianlucam76 deleted the cleanup branch October 30, 2026 13:04
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