Closed zbuchheit closed 4 months ago
https://github.com/pulumi/pulumi-kubernetes/pull/2846 addresses the panic in the Kubernetes provider. There's a question of whether the way YAML sends data impacts any other provider and whether we need to change YAML to send data in the same way as other SDKs.
Closing as fixed by https://github.com/pulumi/pulumi-kubernetes/pull/2846. It's unclear if we need to make any changes in YAML itself.
What happened?
When attempting to use Pulumi Yaml and referencing the privateKey of
gcp:serviceAccount:Key
to use as a kubernetes secret, I hit a panic error.Example
Error
Output of
pulumi about
Additional context
It seem to be present in the create and preview logic. If I create the Key resource first without referencing the privateKey, it will succeed going forward. The same code when converted to typescript works without issue.
Also worth noting the output privateKey is a base64 encoded value.
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).