Output behaviour from YAML programs are drastically different from other languages #705
Labels
kind/bug
Some behavior is incorrect or out of spec
resolution/duplicate
This issue is a duplicate of another issue
What happened?
I'm attempting to use Pulumi YAML as a drop-in replacement for some simple TypeScript Pulumi projects.
When replicating the resources from a TS project to a YAML project, I noticed that the outputs were drastically different, and YAML seems to have a lot of trouble with outputting objects.
Example
Given the following two programs, I would expect identical output (or at least very similar) from both preview and when deployed:
Pulumi YAML
Preview
Note that
nestedbucket
is erroneously assumed to be a string, andwholebucket
is missing literally all of its properties.Post-deploy
Note that
nestedbucket
has now resolved to an object as it should be, butwholebucket
still has no properties.Pulumi in TypeScript
Preview
Note that
nestedbucket
is correctly partially resolved as an object, andwholebucket
has all of its properties.Post-deploy
Output of
pulumi about
Pulumi YAML
(not sure why they're supposedly unknown - according to
pulumi plugin ls
I have a billion versions ofaws
andyaml
is at1.10.0
, which is bundled into pulumi 3.143.0)TypeScript
Additional context
My understanding of the Pulumi ecosystem is that it's meant to allow for consistency across language boundaries, but Pulumi YAML handles outputs very differently from TS. This unfortunately makes Pulumi YAML pretty non-viable for my usecase, because correct previews and outputs for my custom component resources are absolutely critical, and many of them have nested resources that need to be output correctly.
This isn't just a CLI output issue - The outputs are the same on Pulumi Cloud, though I didn't try deploying from/looking at the preview on Cloud.
I also haven't tried with additional languages, as I'm not currently set up to do so.
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).
The text was updated successfully, but these errors were encountered: