The sentry_issue_alert.name attribute is both read-only and required at the same time.

[iabramov]

0.14.3

There is an issue with the "sentry_issue_alert.name" attribute:
Running terraform plan results in the following errors:

If I set the name attribute:

resource "sentry_issue_alert" "backend-new-issues" {
  name         = "backend-new-issues"

terraform plan
╷
│ Error: Invalid Configuration for Read-Only Attribute
│ 
│   with sentry_issue_alert.backend-new-issues,
│   on alerts.tf line 3, in resource "sentry_issue_alert" "backend-new-issues":
│    3:   name         = "backend-new-issues"
│ 
│ Cannot set value for this attribute as the provider has marked it as read-only. Remove the configuration line setting the value.

However, if I remove the name attribute:

resource "sentry_issue_alert" "backend-new-issues" {
  # name         = "backend-new-issues"

terraform plan
 Error: Missing required argument
│ 
│   on alerts.tf line 1, in resource "sentry_issue_alert" "backend-new-issues":
│    1: resource "sentry_issue_alert" "backend-new-issues" {
│ 
│ The argument "name" is required, but no definition was found.

Shouldn’t this attribute not be read-only?
Relevant code references in the provider:

https://github.com/jianyuan/terraform-provider-sentry/blob/v0.14.3/internal/provider/resource_issue_alert.go#L72

[jianyuan]

Hi @iabramov, could you confirm the version of Terraform you were using?

[ThePletch]

I can confirm that I'm seeing identical behavior on version 1.10.5.
with name specified:

│ Error: Invalid Configuration for Read-Only Attribute
│ 
│   with module.project.sentry_issue_alert.slack,
│   on project/alerts.tf line 153, in resource "sentry_issue_alert" "slack":
│  153:   name         = "${var.name} / Slack notification"
│ 
│ Cannot set value for this attribute as the provider has marked it as read-only. Remove the configuration line setting the value.
│ 
│ Refer to the provider documentation or contact the provider developers for additional information about configurable and read-only attributes that are supported.

without name specified:

│ Error: Missing required argument
│ 
│   on project/alerts.tf line 150, in resource "sentry_issue_alert" "slack":
│  150: resource "sentry_issue_alert" "slack" {
│ 
│ The argument "name" is required, but no definition was found.

[ThePletch]

It looks like this is happening because it's marked as both computed and required:

https://github.com/jianyuan/terraform-provider-sentry/blob/v0.14.3/internal/provider/resource_issue_alert.go#L70-L76

https://github.com/jianyuan/terraform-provider-sentry/blob/v0.14.3/internal/provider/resource_issue_alert.go#L45-L47

@jianyuan i'm very unfamiliar with go and the terraform provider package, could this be fixed by just deleting the lines marking the attribute as computed? if so i can put up a quick PR for that.

[cysp]

I also encountered this, and I found that the problem is actually that the diagnostic regarding the read-only name attribute is being mis-reported as applying to the top-level name of the sentry_issue_alert resource, when it actually pertains to the name attributes of sub-objects e.g. each element of conditions_v2, filters_v2 and actions_v2. Those child objects need to be configured without their name attributes, e.g.:

conditions_v2 = [
  { first_seen_event = {} },
  { regression_event = {} },
  { reappeared_event = {} },
  { new_high_priority_issue = {} },
  { existing_high_priority_issue = {} },
]