Morgante Pell

Unfortunately there isn't any way for us to do this. It's core Terraform behavior.

@rux616 This is mostly for backwards-compatibility as historically there were some issues with changing this default. It's definitely worth revisiting our default and you should feel free to set it...

We would probably just output the entire bucket resource. Since this has an easy workaround, marking this as P4. We would be happy to review a PR though.

Can you share the full config?

@jtangney What version of Terraform are you using? This sounds like a potential duplicate of #690, where the fix was to use Terraform 0.12.29.

This seems reasonable, though not a high priority. We would be happy to review a PR.

@jtangney Where is the `var.fl_node_pool_name` variable coming from? Can you try hard-coding it? I'm not sure what is causing this error, since we *don't* use the service account value in...

What version of Terraform are you using? I wonder if this is somehow related to that.

Thanks. Looking at our code, we're using `for_each` correctly (with the name as the key) so I'm not sure why it's raising an error. Could you open an issue on...

I'm fairly sure it's a Terraform core issue. We're using the `name` (fixed) as the key for the `for_each`. The fact that the *value* is indeterminate shouldn't stop Terraform from...