Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Users in DescribeBroker payload is always empty for RabbitMQ #3625

Closed
3 tasks done
yardensachs opened this issue Nov 5, 2020 · 6 comments
Closed
3 tasks done

Users in DescribeBroker payload is always empty for RabbitMQ #3625

yardensachs opened this issue Nov 5, 2020 · 6 comments
Labels
bug This issue is a bug.

Comments

@yardensachs
Copy link

Confirm by changing [ ] to [x] below to ensure that it's a bug:

Describe the bug
Issue with MQ SDK/API - returns an empty list of users in DescribeBroker's payload if it's an AMQ instance with RabbitMQ engine.

Version of AWS SDK for Go?
v1.35.21

Version of Go (go version)?
go version go1.15.2 darwin/amd64

To Reproduce (observed behavior)

  1. Create a new AmazonMQ with RabbitMQ as the engine and add a user.
  2. Call DescribeBroker for that broker you created.
  3. DescribeBroker returns an empty list in DescribeBrokerResponse.Users

Expected behavior
Users list should list the user I created.

Additional context
This issue does not occur with ApacheMQ engine.
Today AmazonMQ launched support for RabbitMQ as an engine.
I am trying to build it into terraform, but this issue causes some problems with the implementation: hashicorp/terraform-provider-aws#16030
I also see this issue in the CLI, boto3 and the AWS console. This is probably an API issue, but I can only open issues here.

@yardensachs yardensachs added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Nov 5, 2020
@yardensachs
Copy link
Author

I also opened a case in amazon support (case id 7577915821)

@KaibaLopez
Copy link
Contributor

Hi @yardensachs,
Could you provide the trace logs of the call? Since this is a new feature it is probable that the sdk is not getting a response from the api call, which would make this a problem with the service (remember to remove sensitive info like credentials).
Here's an example on how to activate logging for service calls

@KaibaLopez KaibaLopez removed the needs-triage This issue or PR still needs to be triaged. label Nov 5, 2020
@yardensachs
Copy link
Author

The API is just not returning the user list really, its not an SDK issue. I opened a support ticket for AWS. I just thought opening here would make it faster to the AWS API team.

@KaibaLopez Should I be closing this?

@KaibaLopez
Copy link
Contributor

@yardensachs ,
Yea, we only keep track of issues specific to the Go SDK here.

Hope it gets addressed soon

@yardensachs
Copy link
Author

lol it did not, they said Users will always be empty with RabbitMQ as the engine, by design

@github-actions
Copy link

github-actions bot commented Nov 6, 2020

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants