Skip to content

Replicated scale-down is a silent no-op — reject or handle #7

Description

@jtomaszon

PR #6 unlocked replicas for edit to support standalone→replicated migration and scale-up. Side effect: decreasing replicas on a replicated Instance (e.g. 3→2) passes Validate() (min 2) but chiNeedsReplicatedMigration() only triggers when current < target — so a decrease is silently ignored. The provider neither scales down nor returns an error; the user sees no effect.

Options

  • Reject scale-down in Validate() with a clear error (simplest, ~5 lines), or
  • Implement safe scale-down (drain/decommission replica, rebalance).

Ref: PR #6 (topology migration). Found in cold review.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions