You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.
[2024-05-10T15:19:36.136Z] │ Error: Provider produced inconsistent result after apply
[2024-05-10T15:19:36.136Z] │
[2024-05-10T15:19:36.136Z] │ When applying changes to
[2024-05-10T15:19:36.136Z] │ module.pagerduty.pagerduty_extension.default["example"], provider
[2024-05-10T15:19:36.136Z] │ "provider[\"[registry.terraform.io/pagerduty/pagerduty\](http://registry.terraform.io/pagerduty/pagerduty/)"]" produced an
[2024-05-10T15:19:36.136Z] │ unexpected new value: .endpoint_url: inconsistent values for sensitive
[2024-05-10T15:19:36.136Z] │ attribute.
[2024-05-10T15:19:36.136Z] │
[2024-05-10T15:19:36.136Z] │ This is a bug in the provider, which should be reported in the provider's
[2024-05-10T15:19:36.136Z] │ own issue tracker.
Expected Behavior
A Successful Apply should occur
Actual Behavior
A failure of Terraform due to inconsistent result
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
We're encountering the identical issue with the same error message here. Temporarily reverting to the previous version of the provider has mitigated the problem for now.
Sensitive values like endpoint_url don't get automatically imported. In a generated file like generated_resources.tf it says endpoint_url = null # sensitive:
It must be replaced with a safe source for this sensitive value (e.g. endpoint_url = var.some_variable_name) before executing terraform apply
Please update your Terraform configuration to use PagerDuty provider v3.13.1 in order to stop facing this issue. Thank you for reporting this issue and for your patience during its resolution.
Hey Pagerduty Team,
Really like the unified results that are starting to happen with the TF Plugin Framework, it looks like we have a regression in
pagerduty_extension
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
terraform init --upgrade
terraform plan -generate-config-out=generated_resources.tf
terraform apply
terraform.required_providers.pagerduty.version
in the providerterraform init --upgrade
terraform apply
<- Where it failsDebug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the
crash.log
.Expected Behavior
A Successful Apply should occur
Actual Behavior
A failure of Terraform due to
inconsistent result
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
Important Factoids
References
pagerduty_service_dependency
to TF Plugin Framework #813The text was updated successfully, but these errors were encountered: