Summary
redisctl enterprise endpoint availability currently fails against the local Enterprise demo cluster, even when basic Enterprise API connectivity is working.
Reproduction
Against the local demo stack on https://localhost:9443:
redisctl enterprise endpoint availability 1 --profile local-enterprise
Observed result:
- command fails with
Failed to check endpoint availability
Expected behavior
One of the following should be true:
- the command succeeds against the demo cluster and returns endpoint availability data, or
- the command detects that the endpoint/operation is unavailable for this cluster version and returns a clear, targeted error
Why this matters
This is a live-cluster mismatch that mock coverage will not catch. We need to verify whether the handler is calling the wrong endpoint, the client is modeling the response incorrectly, or the command needs version-aware behavior.
Acceptance criteria
- Reproduce against the local Enterprise demo stack
- Identify whether the failure is endpoint wiring, response handling, or unsupported server behavior
- Fix the command or improve the error path so the failure mode is explicit
Context
Found during live Enterprise integration testing.
Summary
redisctl enterprise endpoint availabilitycurrently fails against the local Enterprise demo cluster, even when basic Enterprise API connectivity is working.Reproduction
Against the local demo stack on
https://localhost:9443:Observed result:
Failed to check endpoint availabilityExpected behavior
One of the following should be true:
Why this matters
This is a live-cluster mismatch that mock coverage will not catch. We need to verify whether the handler is calling the wrong endpoint, the client is modeling the response incorrectly, or the command needs version-aware behavior.
Acceptance criteria
Context
Found during live Enterprise integration testing.