search

aws / aws-cli

Universal Command Line Interface for Amazon Web Services
Other
15.53k stars 4.13k forks source link

data returned for aws elasticache describe-cache-clusters is incomplete #8309

Closed Dimitry1 closed 11 months ago

Dimitry1 commented 11 months ago

Describe the bug

aws elasticache describe-cache-clusters [ --show-cache-node-info] doesn't return cluser name but only nodes.

Expected Behavior

Expect to find cluster name as part of the returned output. It appears to be that ReplicationGroupId is mapped and used as cluster name.

Current Behavior

there is no cluster name returned

Reproduction Steps

aws elasticache describe-cache-clusters

Possible Solution

If ReplicationGroupId can be mapped and used as Cluster name then it should be documented and/or renamed

Additional Information/Context

No response

CLI version used

aws-cli/2.13.12 Python/3.11.4 Linux/4.18.0-425.3.1.el8.x86_64 exe/x86_64.rhel.8 prompt/off

Environment details (OS name and version, etc.)

rhel 8

tim-finnigan commented 11 months ago

Hi @Dimitry1 thanks for reaching out.

The AWS CLI describe-cache-clusters command corresponds to the ElastiCache DescribeCacheClusters API. If there is any issue with the API functionality, then we recommend reaching out through AWS Support if you have a support plan. We can also escalate API issues to service teams. If your feedback relates to the documentation, then please use the Provide feedback links at the bottom of API documentation pages to reach the appropriate team.

I found there is a CLI example in the ElastiCache User Guide: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Clusters.ViewDetails.html. Is CacheClusterId the return value you are looking for?

I also saw that you referenced the --show-cache-node-info parameter, which can be used "to retrieve information about the individual cache nodes." If you pass --no-show-cache-node-info then do you get the expected results?

github-actions[bot] commented 11 months ago

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.