-
Notifications
You must be signed in to change notification settings - Fork 21
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
Deserialization error while trying to use pulumi-awsgateway #594
Comments
I wasn't able to reproduce this yet, but my working assumption is that:
|
An ongoing effort at reproducing and fixing is being done here: |
We've managed get a new error and more debugging info:
So this one worked:
And this one failed:
|
The resources themselves are:
So the |
This is interesting:
Looks like we send Is that possible? Edit: |
Also, later in the logs, now the stack trace is slightly different:
The type is The
and
Might be just accidentally different ordering of setting the |
Looks like an upstream issue: pulumi/pulumi-aws-apigateway#21 |
Patch was merged upstream, we're waiting for the provider release v0.0.8. |
We have a new error:
|
Auto-closed by the fix addressing the previous issue, re-opening. |
I can see no other reason for this than the provider returning the wrong object then a bug:
|
I've reported upstream: pulumi/pulumi-aws-apigateway#41 |
I'm trying to follow the discussion but only the issue description from @slnowak is making sense to me. I can reproduce with:
Which gives me the original exception:
|
I can confirm I get this when upgrading SDK to the tip of
|
yes, this is what we've got from the provider, the URN is wrong for |
Reproducing with latest versions from main: |
Adding more debugging messages reveal this raw
What I found interesting is that |
We have this pulumi-java/sdk/java/pulumi/src/main/java/com/pulumi/deployment/internal/DeploymentImpl.java Line 856 in cb3c1b1
And according to the logs |
Debugging this further I believe this is a bug in the provider. Legit looks like a typo. I cannot reproduce after this fix: Stay tuned for an updated version of the provider after my fix is reviewed and released. |
What happened?
When trying to run a minimalistic example with
aws-apigateway
, pulumi throws the following error:Steps to reproduce
Use the following code snippet:
maven dependencies:
Both awsx and aws-apigateway artifacts were built locally from the following git commit:
Expected Behavior
Successfull execution
Actual Behavior
Execution error
Versions used
No response
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).
The text was updated successfully, but these errors were encountered: