This message was deleted.

Related issue https://github.com/pulumi/pulumi-gcp/issues/291

Interesting. I would not have expected that resource to work in Terraform either. But if it does, then this is a bug in the Pulumi Terraform bridge handling of default application.

@white-balloon-205 actually I mapped the pulumi config to terraform there, I did not reproduce it. I also found their tests which do cover this area quite well so right now Pulumi Terraform Bridge is the main suspect

Got it - so this is then a bug in the Pulumi Terraform Bridge.

Is there a general guide on how to debug the output Pulumi send to terraform?

See https://www.pulumi.com/docs/troubleshooting/#verbose-logging for verbose logs which will include the values marshalled to and from all provider calls. But if the bug is what we are assuming here - I expect this will show that the default is being applied earlier that Terraform would apply it, and thus triggering the ExactlyOneOf.

So I ran the script with logging enabled and we can indeed see the default value being applied. You can clearly see the input value being just the ‘values’ list, and then a few steps later ‘all’ is applied.