Closed nstires-ctgx closed 11 months ago
Could it be a regression or related to https://github.com/pulumi/pulumi-yaml/issues/298 ?
Hello @nstires-ctgx thank you for filing the issue and for the detailed report š this is definitely a bug. protect
should accept dynamic values regardless of where they come from (unless they are unknowns). We will fix this as soon as possible
@Zaid-Ajaj - I'm fairly sure protect
cannot accept dynamic values that are Outputs, but config
keys are definitely acceptable.
What happened?
When a config value is declared, and a default is passed, it's changing the type of the value to string.
On
pulumi up
:Expected Behavior
Default value should be accepted and passed as bool.
Steps to reproduce
Pulumi.yaml:
Note that:
true
orfalse
in the resource option works as expectedOutput of
pulumi about
Additional context
No response
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).