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

[Enhancement]: aws_mq_broker does not need to reboot on changes to maintenance_window_start_time or auto_minor_version_upgrade #37797

Closed
SignalWhisperer opened this issue Jun 1, 2024 · 4 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/mq Issues and PRs that pertain to the mq service.

Comments

@SignalWhisperer
Copy link
Contributor

Description

Rebooting an Amazon MQ broker is not necessary for modifications to maintenance_window_start_time or to auto_minor_version_upgrade. These changes take effect immediately.

Affected Resource(s) and/or Data Source(s)

  • aws_mq_broker

Potential Terraform Configuration

No response

References

Would you like to implement a fix?

Yes

@SignalWhisperer SignalWhisperer added the enhancement Requests to existing resources that expand the functionality or scope. label Jun 1, 2024
Copy link

github-actions bot commented Jun 1, 2024

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/mq Issues and PRs that pertain to the mq service. label Jun 1, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Jun 1, 2024
@SignalWhisperer
Copy link
Contributor Author

Resolved by #36506

Copy link

github-actions bot commented Jun 7, 2024

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

@terraform-aws-provider terraform-aws-provider bot removed the needs-triage Waiting for first response or review from a maintainer. label Jun 7, 2024
Copy link

github-actions bot commented Jul 8, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/mq Issues and PRs that pertain to the mq service.
Projects
None yet
Development

No branches or pull requests

1 participant