Garret Pick
Garret Pick
I also recently ran into this limitation where I needed to update the route table for a VPC to VPC peering connection. If the route tables where created without the...
@jpvajda those were dummy names I used for the PR. These are the actual ``` - data.newrelic_entity.firestorm_service_prod_useast.application_id + # TODO - the following returns 705936293 ?? + # data.newrelic_entity.firestorm_service_prod_useast.application_id ```...
@jpvajda - I just realized that I didn't include the actual name of the entity/application above. ``` # TODO # data "newrelic_entity" "firestorm_service_prod_useast" { data "newrelic_application" "firestorm_service_prod_useast" { name =...
@jpvajda we were trying to modify an existing and replace the `newrelic_application` data source which is being deprecated per the warning above with `newrelic_entity`
@ctrombley please see my recent comments above. We are using `data.newrelic_entity.service1.application_id` and it returns a different ID from when we used `data.newrelic_application.service.id` We have a meeting setup with our account...
@ctrombley - that definitely sounds like it could be the issue. Thanks! I'm having trouble with the work-around you suggested. ``` Error: Unsupported argument on data.tf line 47, in data...
@ctrombley thank you! Specifying the accountID via the tag in the data source does indeed work-around the issue. Looking forward to the official fix.
> The problem appears to have originated from the registry and numerous incorrectly cached responses. Please let us know if there are any modules which continue to exhibit this behavior...
I've confirmed everything is working for me with `1.2.7` now. Note that running `terraform init -upgrade` may be an alternative to manually removing the `.terraform` directory. Thanks for the quick...