terraform-provider-newrelic: Upgrade to v1.12.0 breaks "newrelic_alert_channel" data source implementatiom
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
Affected Resource(s)
Please list the resources as a list, for example:
- newrelic_alert_channel data source
If this issue appears to affect multiple resources, it may be an issue with Terraform’s core, so please mention this.
Terraform Configuration Files
data "newrelic_alert_channel" "email_alert_channels" {
name = format("%s_alert_channel", "service-name")
}
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.
Debug 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. https://gist.github.com/SiddhantAgarwal17/ae9e7b02884e280e02ab564abb7d11e4
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.
Expected Behavior
It should have matched with the service-name_alert_channel format as with v1.10.0 and earlier.
Actual Behavior
It failed to match with the name even though the channel with that name exists in New Relic.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
Important Factoids
Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs? No
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
- GH-1234
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (7 by maintainers)
@SiddhantAgarwal17 This issue has been resolved in v1.13.1. Please let us know if you run into other issues.
Quick follow-up, @piechu’s discovery seems to be correct. We’ll be working to get this fixed. Thanks for the report.