Closed Muchaszewski closed 3 months ago
Note, that after replacing all providers like that there are further errors as if the DLLs with plugins/modules were not loaded at all.
Video with debugger attached on how the issue looks, step into and step over generate the same result:
https://github.com/user-attachments/assets/36cd252f-7796-4c97-921d-68810bf71ca0
Compilation result folder has all the DLLs, and they all contain all correct definitions (after decompilation)
Hi there @Muchaszewski thanks a lot for filing the issue! :pray: any chance you could try the reverting Pulumi
from v3.66.0
to v3.65.0
or removing the Pulumi
nuget package entirely? (since it is a dependency of the providers)
We did add a new optional parameter for the constructor of Provider
:
public ProviderResource(
string package,
string name,
ResourceArgs args,
CustomResourceOptions? options = null)
became:
public ProviderResource(
string package,
string name,
ResourceArgs args,
CustomResourceOptions? options = null,
RegisterPackageRequest? registerPackageRequest = null)
Which I assumed to be non a breaking change (the new parameter is optional) but it looks like existing .NET SDKs built with older versions of Pulumi looks for that exact parameter, regardless of optionalness (not binary compatible)
I can repro using the provider from Pulumi.Random
v4.16.3 (built with Pulumi v.3.64.0) and it gives the same error
Hi @Muchaszewski version 3.66.1 has been published and I've tested that the issue no longer appears with providers, invokes or resources. Please give it a try and let us know if you encounter any issues.
The error is gone! Thank you for your fast response and for fixing the issue!
What happened?
Instantiate new provider from code
or
This code worked ~3 months ago, and I did change nothing in my code base. Now I could finally get back to this deployment and I encountered the following issue on ALL providers.
Right now, after running this code for all providers, I get this error.
I tried:
The only thing that helps is copy-pasting the decompiled code, and implementing it manually and using that instead. But this workaround is messy and I wish I would not have to do that.
Example
or
Exception
Output 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).