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

The attribute "integration_key" is deprecated. Refer to the provider documentation for details #799

Closed
kingferiol opened this issue Jan 12, 2024 · 3 comments · Fixed by #801

Comments

@kingferiol
Copy link

Hi there,

We are receiving the following warning

Warning: Deprecated attribute

  on ../pagerduty-service/sns-topic.tf line 14, in resource "aws_sns_topic_subscription" "pagerduty_cloudwatch":
  14:   endpoint = "https://events.pagerduty.com/integration/${pagerduty_service_integration.cloudwatch.integration_key}/enqueue"

The attribute "integration_key" is deprecated. Refer to the provider documentation for details.

But on the documentation (https://registry.terraform.io/providers/PagerDuty/pagerduty/latest/docs/resources/service_integration), I can still find this example

To configure an event, please use the integration_key in the following interpolation:

https://events.pagerduty.com/integration/${pagerduty_service_integration.slack.integration_key}/enqueue

Thanks for all the help/support

Terraform Version

1.6

Plugin version

3.4.0

@gopipalamalai
Copy link

gopipalamalai commented Jan 13, 2024

Seems like according to this change https://github.com/PagerDuty/terraform-provider-pagerduty/pull/775/files it can be used as read-only, but not as input in an upcoming major release.

"integration_key": {
				Type:       schema.TypeString,
				Optional:   true,
				Computed:   true,
				Deprecated: "Assignments or updates to this attribute are not supported by Service Integrations API, it is a read-only value. Input support will be dropped in upcomming major release",

@kingferiol
Copy link
Author

Hi @gopipalamalai

Thanks for your answer.

At this point what's the correct implementation to drop the WARNING?

Best

Maurizio

@gopipalamalai
Copy link

We are using it has read only, attribute reference, in our code so we are ignoring the warning. Not sure what the alternative workaround is if this is used as input argument.

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

Successfully merging a pull request may close this issue.

2 participants