Skip to content

Make predictable order of API endpoints returned by AWS MQ API#47777

Open
avoidik wants to merge 1 commit intohashicorp:mainfrom
avoidik:predictable-mq-endpoints-order
Open

Make predictable order of API endpoints returned by AWS MQ API#47777
avoidik wants to merge 1 commit intohashicorp:mainfrom
avoidik:predictable-mq-endpoints-order

Conversation

@avoidik
Copy link
Copy Markdown
Contributor

@avoidik avoidik commented May 6, 2026

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

Description

Relations

Closes #47764

References

Output from Acceptance Testing

% make testacc TESTS=TestAccXXX PKG=ec2

...

@avoidik avoidik requested a review from a team as a code owner May 6, 2026 09:22
@dosubot dosubot Bot added the bug Addresses a defect in current functionality. label May 6, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

  • Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
  • Please see our prioritization guide for additional information on how the maintainers handle prioritization.
  • Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

  • Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
  • Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

✅ Thank you for correcting the previously detected issues! The maintainers appreciate your efforts to make the review process as smooth as possible.

@github-actions github-actions Bot added needs-triage Waiting for first response or review from a maintainer. documentation Introduces or discusses updates to documentation. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure. service/mq Issues and PRs that pertain to the mq service. size/L Managed by automation to categorize the size of a PR. labels May 6, 2026
@avoidik avoidik force-pushed the predictable-mq-endpoints-order branch 2 times, most recently from 9d51e0f to 5d759c9 Compare May 6, 2026 10:37
@avoidik avoidik force-pushed the predictable-mq-endpoints-order branch from 5d759c9 to 963da2f Compare May 6, 2026 11:12
@github-actions github-actions Bot added size/XL Managed by automation to categorize the size of a PR. and removed size/L Managed by automation to categorize the size of a PR. labels May 6, 2026
@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label May 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Addresses a defect in current functionality. documentation Introduces or discusses updates to documentation. service/mq Issues and PRs that pertain to the mq service. size/XL Managed by automation to categorize the size of a PR. tests PRs: expanded test coverage. Issues: expanded coverage, enhancements to test infrastructure.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aws_mq_broker incorrect order of endpoints due to the new feature (prometheus monitoring)

2 participants