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

azurerm_eventgrid_topic - several arguments in "input_mapping_fields" object have no effect #19490

Closed
1 task done
kbargobdo opened this issue Nov 29, 2022 · 4 comments · Fixed by #19494
Closed
1 task done
Labels
Milestone

Comments

@kbargobdo
Copy link

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 "+1" or "me too" comments, 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

Terraform Version

1.2.7

AzureRM Provider Version

3.33.0

Affected Resource(s)/Data Source(s)

azurerm_eventgrid_topic

Terraform Configuration Files

resource "azurerm_eventgrid_topic" "eventgrid_topic" {
  name                          = "test-egt"
  resource_group_name           = "test-rg"
  location                      = "northcentralus"
  input_schema                  = "CustomEventSchema"
  local_auth_enabled            = true
  public_network_access_enabled = true

  identity {
      type = "SystemAssigned"
  }

  input_mapping_fields {
      data_version = "data"
      event_time   = "time"
      event_type   = "event"
      id           = "id"
      subject      = "subject"
      topic        = "topic"
  }

  input_mapping_default_values {
      data_version = "testdata"
      event_type   = "testtype"
      subject      = "testsubject"
  }

  lifecycle {
    ignore_changes = [
      # Ignore changes to tags, e.g. because a management agent
      # updates these based on some ruleset managed elsewhere.
      tags
    ]
  }
}

Debug Output/Panic Output

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  + resource "azurerm_eventgrid_topic" "eventgrid_topic" {
      + endpoint                      = (known after apply)
      + id                            = (known after apply)
      + input_schema                  = "CustomEventSchema"
      + local_auth_enabled            = true
      + location                      = "northcentralus"
      + name                          = "test-egt"
      + primary_access_key            = (sensitive value)
      + public_network_access_enabled = true
      + resource_group_name           = "test-rg"
      + secondary_access_key          = (sensitive value)

      + identity {
          + principal_id = (known after apply)
          + tenant_id    = (known after apply)
          + type         = "SystemAssigned"
        }

      + input_mapping_default_values {
          + data_version = "testdata"
          + event_type   = "testtype"
          + subject      = "testsubject"
        }

      + input_mapping_fields {
          + data_version = "data"
          + event_time   = "time"
          + event_type   = "event"
          + id           = "id"
          + subject      = "subject"
          + topic        = "topic"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.
azurerm_eventgrid_topic.eventgrid_topic: Creating...
azurerm_eventgrid_topic.eventgrid_topic: Still creating... [10s elapsed]
azurerm_eventgrid_topic.eventgrid_topic: Creation complete after 12s [id=/subscriptions/*******/resourceGroups/test-rg/providers/Microsoft.EventGrid/topics/test-egt]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Expected Behaviour

The Azure Event Grid Topic should be deployed and both the "input_mapping_fields" and "input_mapping_default_values" objects should be set to the values defined in the resource deployment. See below:

InputMappingField : {[id, id], [topic, topic], [eventtime, time], [eventtype, event], [subject, subject], [dataversion, data]}
InputMappingDefaultValue : {[eventtype, testtype], [subject, testsubject], [dataversion, testdata]}

Actual Behaviour

The Azure Event Grid Topic resource deploys, but the "event_type", "subject", and "data_version" values for "input_mapping_fields" are missing and not set. See below:

Using Az PowersShell cmdlet to pull the fields and default values from Azure.

InputMappingField : {[id, id], [topic, topic], [eventtime, time]}
InputMappingDefaultValue : {[eventtype, testtype], [subject, testsubject], [dataversion, testdata]}

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@sinbai
Copy link
Contributor

sinbai commented Nov 30, 2022

@kbargobdo thanks for raising this issue here. I have submitted PR to fix it. Could you keep track of it for more updates?

@kbargobdo
Copy link
Author

@sinbai - thanks so much! I have subscribed to the PR - looking forward to it getting merged up!

@github-actions github-actions bot added this to the v3.34.0 milestone Dec 1, 2022
@github-actions
Copy link

github-actions bot commented Dec 2, 2022

This functionality has been released in v3.34.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

github-actions bot commented Jan 2, 2023

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 Jan 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
3 participants