New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pulumi automation can not handle objectValue in Config #6809
Comments
I believe this is a duplicate of #5506, which has some suggestions for potential workarounds. |
Hi, okay looking at this again I think I see what's going on here and it's not exatcly a dupe of #5506. This looks like something I fixed previously but it's possible there's been a regression. @ncd it looks like you're using automation API with python. Is that right? What version are you using? Can you share more of your automation code? |
Okay, I just rechecked that we did indeed fix this issue in Pulumi 2.21.0 and we have tests for it, so I'm going to close this out. If you are using the latest version and are somehow still hitting this error, please reopen. |
I'm striking the same issue. I have a similar code & setup as the local python example generates the following stacktrace immediately after performing the
FWIW, |
@komalali Thank Komal, the updated code has fixed my issue. Besides, as I checked, the issue also happen in other languagues' automation package. |
I made pulumi config as an object.
When I run stack refresh/up using pulumi.x.automation module --> I always failed due to an error: unexpected keyword argument 'objectValue'.
Recheck with pulumi stack history command:
Expected behavior
The code will run normally
Current behavior
The code has error
Steps to reproduce
Context (Environment)
Affected feature
The text was updated successfully, but these errors were encountered: