You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when PULUMI_ERROR_OUTPUT_STRING="true" option is used, and there is an output in the triggers array, the pulumi throws an error that toString was called on an Output
Example
set env variable PULUMI_ERROR_OUTPUT_STRING="true"
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:
I was able to repro this on my local machine when using @pulumi/pulumi version 1.133.0, but it appears to be fixed when using version 1.137.0
We did have a regression in @pulumi/pulumi version 1.133.0 that, while not identical with this issue, probably shared the same root cause, so I suspect it was resolved by the same PR.
Please reopen if upgrading the version does not help.
What happened?
when
PULUMI_ERROR_OUTPUT_STRING="true"
option is used, and there is an output in thetriggers
array, the pulumi throws an error that toString was called on an OutputExample
set env variable
PULUMI_ERROR_OUTPUT_STRING="true"
have output in the
triggers
arrayyou get error:
minimal_working_example.zip
Output of
pulumi about
CLI
Version 3.133.0
Go Version go1.23.1
Go Compiler gc
Plugins
KIND NAME VERSION
resource command 1.0.1
language nodejs unknown
Host
OS Microsoft Windows 11 Enterprise
Version 10.0.22631 Build 22631
Arch x86_64
This project is written in nodejs: executable='C:\Program Files\nodejs\node.exe' version='v20.15.0'
Current Stack: organization/temp/dev
TYPE URN
pulumi:pulumi:Stack urn:pulumi:dev::temp::pulumi:pulumi:Stack::temp-dev
pulumi:providers:command urn:pulumi:dev::temp::pulumi:providers:command::default_1_0_1
command:local:Command urn:pulumi:dev::temp::command:local:Command::cmd
Additional context
workaround is to wrap the whole array in an output
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: