fix(enterprise): resolve command issues found in v0.5.0 spot checks

[joshrotenberg]

Overview

During spot checks of v0.5.0, several enterprise commands were found to have issues. This is a tracking issue for fixing all of them.

Testing Environment

• Redis Enterprise: kurtfm/rs-arm:latest (ARM64)
• redisctl: v0.5.0 + local fixes from PR fix: init-cluster workflow authentication and docker-compose setup #314
• Cluster initialized with enterprise workflow init-cluster

Working Commands ✅

• enterprise workflow init-cluster - Successfully bootstrapped cluster
• enterprise bootstrap status - Shows completed status correctly
• enterprise database create - Created test-db successfully
• enterprise database list - Lists active database
• enterprise node list - Shows node information
• enterprise license get - Shows trial license
• enterprise acl list - Shows default ACL
• api enterprise get /v1/cluster - Raw API access works

Commands with Issues ❌

Response Parsing Errors

• fix(enterprise): cluster get command fails with "error decoding response body" #316 - enterprise cluster get - "error decoding response body"
• fix(enterprise): user list command fails with "error decoding response body" #317 - enterprise user list - "error decoding response body"

Commands that Hang/Timeout

• fix(enterprise): alerts get-settings command hangs/times out #318 - enterprise alerts get-settings - Hangs/times out
• fix(enterprise): ldap get-config command hangs/times out #319 - enterprise ldap get-config - Hangs/times out
• fix(enterprise): ocsp get command hangs/times out #320 - enterprise ocsp get - Hangs/times out
• fix(enterprise): debug-info list command hangs/times out #321 - enterprise debug-info list - Hangs/times out

Other Errors

• fix(enterprise): services list command returns error/empty response #322 - enterprise services list - Returns error/empty response

Root Causes (Likely)

1. Type definition mismatches - Response types don't match actual API responses
2. Missing or incorrect handlers - Some handlers may not be properly implemented
3. API endpoint issues - Some endpoints may not exist or behave differently than expected

Success Criteria

• All listed commands work correctly against a bootstrapped Redis Enterprise cluster
• Proper error messages for legitimate failures (instead of parsing errors or hangs)
• Integration tests added for each fixed command

Progress

Sub-issues created for each problem. Fix these one by one and check them off as completed.

[joshrotenberg]

Status Update

✅ Resolved Issues

Deserialization Errors (Fixed in PR #327)

• fix(enterprise): cluster get command fails with "error decoding response body" #316, enterprise user list command fails with deserialization error #323, enterprise cluster get command fails with deserialization error #325 - enterprise cluster get - Fixed type mismatches in ClusterInfo struct
• fix(enterprise): user list command fails with "error decoding response body" #317, enterprise user list command fails with deserialization error #323 - enterprise user list - Fixed User struct (removed username, made email required)
• enterprise cluster get-license command fails with deserialization error #324 - enterprise cluster get-license - Fixed License struct field issues

Invalid/Non-existent Commands (Closed as invalid)

• fix(enterprise): alerts get-settings command hangs/times out #318 - alerts get-settings - Actually works, returns alert settings from cluster config
• fix(enterprise): ldap get-config command hangs/times out #319 - ldap get-config - Command doesn't exist, correct command is ldap get
• fix(enterprise): ocsp get command hangs/times out #320 - ocsp get - Actually works correctly
• fix(enterprise): debug-info list command hangs/times out #321 - debug-info list - Command doesn't exist, available commands are all, node, database

Wrong Endpoint (Fixed in PR #328)

• fix(enterprise): services list command returns error/empty response #322 - services list - Was using /v1/services, fixed to use /v1/local/services

📊 Summary

• Total Issues: 10 (7 sub-issues from this tracking issue)
• Fixed: 5 (deserialization errors + wrong endpoint)
• Invalid: 4 (commands that don't exist or were already working)
• Remaining: 0

All originally reported enterprise command issues have been addressed!