MQ DescribeBroker call doesn't return RabbitMQ users

[mattburgess]

Originally raised at aws/aws-sdk-go#3625

Given an input.json of:

{
    "BrokerName": "mybroker",
    "DeploymentMode": "SINGLE_INSTANCE",
    "EngineType": "RABBITMQ",
    "EngineVersion": "3.8.6",
    "HostInstanceType": "mq.t3.micro",
    "StorageType": "EBS",
    "Users": [
        {
            "Password": "TestTest1234",
            "Username": "Test"
        }
    ]
}

The cluster can be created using: aws mq create-broker --cli-input-json file://input.json

And then described using: aws mq describe-broker --broker-id b-6f570b6d-319c-4ce6-abb0-4d2068c57cf9

This shows:

{
    "AuthenticationStrategy": "simple",
    "AutoMinorVersionUpgrade": true,
    "BrokerArn": "arn:aws:mq:us-west-2:xxx:broker:mybroker:b-6f570b6d-319c-4ce6-abb0-4d2068c57cf9",
    "BrokerId": "b-6f570b6d-319c-4ce6-abb0-4d2068c57cf9",
    "BrokerInstances": [
        {
            "ConsoleURL": "https://b-6f570b6d-319c-4ce6-abb0-4d2068c57cf9.mq.us-west-2.amazonaws.com",
            "Endpoints": [
                "amqps://b-6f570b6d-319c-4ce6-abb0-4d2068c57cf9.mq.us-west-2.amazonaws.com:5671"
            ]
        }
    ],
    "BrokerName": "mybroker",
    "BrokerState": "RUNNING",
    "Created": "2020-12-22T16:53:38.703Z",
    "DeploymentMode": "SINGLE_INSTANCE",
    "EncryptionOptions": {
        "UseAwsOwnedKey": true
    },
    "EngineType": "RabbitMQ",
    "EngineVersion": "3.8.6",
    "HostInstanceType": "mq.t3.micro",
    "Logs": {
        "General": false,
        "GeneralLogGroup": "/aws/amazonmq/broker/b-6f570b6d-319c-4ce6-abb0-4d2068c57cf9/general"
    },
    "MaintenanceWindowStartTime": {
        "DayOfWeek": "TUESDAY",
        "TimeOfDay": "03:00",
        "TimeZone": "UTC"
    },
    "PubliclyAccessible": false,
    "SecurityGroups": [
        "sg-0e3470cde0f9f4f73"
    ],
    "StorageType": "ebs",
    "SubnetIds": [
        "subnet-0d09a732b68bd3467"
    ],
    "Tags": {},
    "Users": []
}

Note how the Users array is empty. This causes problems for anything that's trying to perform drift detection, e.g. Terraform (see hashicorp/terraform-provider-aws#16751) as it now can't tell whether the correct user has been configured.

[vudh1]

Closing this because the service team discussed that implementation of this feature will require som breaking changes.

[github-actions]

This issue is now closed.

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.