New Resource: azurerm_email_communication_service_domain_sender_username

[neil-yechenwei]

Community Note

• Please vote on this PR by adding a 👍 reaction to the original PR to help the community and maintainers prioritize for review
• Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for PR followers and do not help prioritize for review

Description

This PR is to support new resource azurerm_email_communication_service_domain_sender_username.

API reference: azure-rest-api-specs/specification/communication/resource-manager/Microsoft.Communication/stable/2023-04-01/SenderUsernames.json at 7a4e5f767bcdb06d25544975e706a7e9f85a586b · Azure/azure-rest-api-specs

PR Checklist

• I have followed the guidelines in our Contributing Documentation.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have checked if my changes close any open issues. If so please include appropriate closing keywords below.
• I have updated/added Documentation as required written in a helpful and kind way to assist users that may be unfamiliar with the resource / data source.
• I have used a meaningful PR title to help maintainers and other users understand this change and help prevent duplicate work.
  For example: “resource_name_here - description of change e.g. adding property new_property_name_here”

Changes to existing Resource / Data Source

• I have added an explanation of what my changes do and why I'd like you to include them (This may be covered by linking to an issue above, but may benefit from additional explanation).
• I have written new tests for my resource or datasource changes & updated any relevant documentation.
• I have successfully run tests with my changes locally. If not, please provide details on testing challenges that prevented you running the tests.
• (For changes that include a state migration only). I have manually tested the migration path between relevant versions of the provider.

Testing

• My submission includes Test coverage as described in the Contribution Guide and the tests pass. (if this is not possible for any reason, please include details of why you did or could not add test coverage)

Change Log

Below please provide what should go into the changelog (if anything) conforming to the Changelog Format documented here.

• New Resource: azurerm_email_communication_service_domain_sender_username

This is a (please select all that apply):

• Bug Fix
• New Feature (ie adding a service, resource, or data source)
• Enhancement
• Breaking Change

Related Issue(s)

Fixes #22549

Note

If this PR changes meaningfully during the course of review please update the title and description as required.

[ms-zhenhua]

Hi @neil-yechenwei ,

Thanks for this PR - I've taken a look through and left some comments inline. If we can fix those up, this should be good to go 👍

[neil-yechenwei]

@ms-zhenhua , thanks for the comments. I updated PR. Please take another look. Below is the latest test result.

[neil-yechenwei]

@ms-zhenhua , thanks for the comments. I replied the comments. Please take another look.

[ms-zhenhua]

@neil-yechenwei ,

Thanks for the updates. LGTM~

[navesimchi]

@neil-yechenwei @ms-zhenhua Just checking in — do you have an estimated release date for this change?

[lonegunmanb]

Hi @navesimchi we just have an AVM Terraform module which supports this new resource: https://registry.terraform.io/modules/Azure/avm-res-communication-emailservice/azurerm/latest

[sreallymatt]

Thanks @neil-yechenwei, LGTM

[github-actions]

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