enterprise database create --dry-run returns 404 instead of validating request

[jeremyplichta]

Summary

redisctl enterprise database create --dry-run appears to call a nonexistent API path and fails with 404 Not Found instead of validating or previewing the request.

Repro

Profile was a working Redis Enterprise cluster (jp-flex1) where normal database creation succeeds.

cat >/tmp/jp-flex1-db1.json <<'JSON'
{
  "name": "jp-flex1-db1",
  "type": "redis",
  "redis_version": "8.6",
  "port": 12000,
  "bigstore": true,
  "bigstore_version": 2,
  "memory_size": 354334801920,
  "bigstore_ram_size": 32212254720,
  "replication": false,
  "sharding": false,
  "data_persistence": "disabled",
  "eviction_policy": "noeviction",
  "proxy_policy": "single"
}
JSON

redisctl -p jp-flex1 enterprise database create --data @/tmp/jp-flex1-db1.json --dry-run -o json

Actual result

API error: 404 Not Found: The requested resource does not exist

Expected result

--dry-run should either:

• validate the payload without creating the database, or
• return a clear "dry-run not supported" error from the CLI before making the request.

It should not hit a nonexistent API endpoint and return a generic 404.

Notes

Normal create on the same cluster and profile works.

redisctl -p jp-flex1 enterprise database create --data @/tmp/jp-flex1-db1.json -o json

That confirms the bug is specific to the CLI dry-run path, not the payload or cluster.