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

[CSGI-2268 ] Deprecate integration_key attribute mutation for Service Integrations #775

Conversation

imjaroiswebdev
Copy link
Contributor

Closes #549

Since Service Integration creation through POST /services/{id}/integrations doesn't support passing in the field integration_key a deprecation warning for it is being introduced with this update.

After this update Provider will display following warning when pagerduty_service_integration.integration_key receives any assignments...

╷
│ Warning: Argument is deprecated
│
│   with pagerduty_service_integration.apiv2,
│   on main.tf line 57, in resource "pagerduty_service_integration" "apiv2":
│   57:   integration_key = "12345678910testtesttesttesttes"
│
│ Assignments or updates to this attribute are not supported by Service Integrations API, it is
│ a read-only value. Input support will be droped in upcomming major release

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 this pull request may close these issues.

pagerduty_service_integration shouldn't allow setting integration_key, at least for "API V2"
1 participant