Open danielrbradley opened 1 week ago
Thanks for the detailed issue!
Is there a rough ETA on when this fix will be implemented?
@markdebeer we do not have an ETA. Which provider are you using which hits this problem? If this is in AzureDevOps, can you please comment on the issue there with your use case and we might be able to prioritize a workaround instead.
EDIT: my bad, just noticed you opened the issue https://github.com/pulumi/pulumi-azuredevops/issues/514
@danielrbradley can we consider a workaround for the problem in the provider?
In the Azure DevOps provider, we've encountered an issue where the upstream provider explicitly expects values to be null.
The schema for the sub-property is defined as:
Sample program:
During the create and update the following code is executed which appears to work correctly in TF but fails via the bridge:
The variables inside the loop resolve to:
gRPC request:
Props in the Pulumi provider ready to be sent to the TF provider
Provider issue: