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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Communication Service connected email domain gets deleted after updating the tag through Terraform #26495

Open
1 task done
sahadkp-dlt opened this issue Jun 27, 2024 · 1 comment

Comments

@sahadkp-dlt
Copy link

sahadkp-dlt commented Jun 27, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

v1.8.3

AzureRM Provider Version

3.65.0

Affected Resource(s)/Data Source(s)

azurerm_communication_service

Terraform Configuration Files

provider "azurerm" {
  features {}
}

resource "azurerm_communication_service" "this" {
  name = "${var.project}-${var.environment}-communication-service"

  resource_group_name = var.resource_group.name
  data_location       = var.conf.data_location

  tags = var.tags
}

Debug Output/Panic Output

Communication service connected email domain is deleted

Note:
Their is no terraform argument-reference in the azurerm_communication_service for connecting email domain created in azurerm_email_communication_service

Expected Behaviour

No response

Actual Behaviour

communication service connected email domain is deleted

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@neil-yechenwei
Copy link
Contributor

Thanks for raising this issue. I can't reproduce this issue with below tf config that is similar with yours. Could you try latest tf azurerm provider and below tf config to see if the issue still exists? Thanks.

provider "azurerm" {
  features {}
}

resource "azurerm_resource_group" "test" {
  name     = "acctestRG-communicationservice-test01"
  location = "westeurope"
}

resource "azurerm_communication_service" "test" {
  name                = "acctest-CommunicationService-test01"
  resource_group_name = azurerm_resource_group.test.name
  data_location       = "United States"

  tags = {
    env = "Test2"
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants