https://cloudposse.com logo
Join Slack
Powered by
`terraform-provider-utils` plugin error
# terraform
r
terraform-provider-utils
plugin error
Getting this error on v1.31.0. It looked to be addressed in v2.0.0, but the error is persisting:
Copy code
│ Error: Plugin did not respond
│ 
│   with module.spacelift_stacks_config.module.spacelift_config.data.utils_spacelift_stack_config.spacelift_stacks,
│   on .terraform/modules/spacelift_stacks_config.spacelift_config/modules/spacelift/main.tf line 1, in data "utils_spacelift_stack_config" "spacelift_stacks":
│    1: data "utils_spacelift_stack_config" "spacelift_stacks" {
│ 
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ReadDataSource call. The plugin logs may contain
│ more details.
Are there other considerations I may be missing in getting past this? OpenTofu need to be past a particular version or for some reason the Atmos version on our image? Our config should be behind the stated cause. Or is it related to Issue 521 and ongoing?
e
@Andriy Knysh (Cloud Posse) heads up
a
it was suposed to be fixed in https://github.com/cloudposse/terraform-provider-utils/pull/523 and released as v2.0.1, but the GitHub action failed and it was not released. We'll cut a new release @RickA
r
Turns out I was a dummy. A coworker found my own PR where I put 
{}
instead of 
[]
and that broke it. Sorry to waste everyone's time. 😞
a
thanks @RickA that's interesting, 
{}
should not break the provider, it should show an error - we'll review it
@RickA we have released a new utils provider version https://github.com/cloudposse/terraform-provider-utils/releases/tag/v2.0.2 it includes the fixes from https://github.com/cloudposse/terraform-provider-utils/pull/523 not related to "`{}` instead of 
[]
and that broke it", but should work better when terraform calls the provider functions concurrently
r
Cheers, thank you. 👍 Coworker read the details of the error better than I did and sniffed out what I did. It's nice to have smart teammates. 😇 I saw the plugin error message and that it was attributed to a submodule and jumped to conclusions. Bolstered by the similar error in that issue posted in the repo. So all this was user error and I'll try to do better.
e
Thanks, @RickA! No worries. Sometimes just having a sounding board is helpful.
6 Views
Open in Slack
PreviousNext
Powered by