big-architect-71258
02/06/2024, 11:58 AMMuxWith
Property on the ProviderInfo
struct. https://github.com/pulumi/pulumi-terraform-bridge/blob/f2504a55bf4289b93cad1cb7d54165bbb3af9c68/pkg/tfbridge/info.go#L137
A sample how to use the Muxer can be found in my Pulumi Azure repo.
https://github.com/tmeckel/pulumi-azure/commits/feat/mux-provider-go/worried-energy-90920
03/03/2024, 4:25 PMbig-architect-71258
03/03/2024, 4:43 PMprov.MustComputeTokens
2. Use the module_overrides
map, to map resources and data sources to there old names. This would have the benefit of utilizing the automapper and will ease any upgrades of the upstream TF provider. One warning here: ensure that you don't end up with mixture of new old old module names, which will clutter up the namespaces of programming language SDKs.
3. Use the automapper as is and define aliases for the re-mapped "old" resources to the new naming schema. https://www.pulumi.com/docs/concepts/options/aliases/ But that would mean that everybody who used the provider in the past MUST define those aliases. So to me the least favorable alternative.big-architect-71258
03/03/2024, 4:44 PMbig-architect-71258
03/03/2024, 4:48 PMworried-energy-90920
03/03/2024, 5:27 PMmodule_overrides
map since i'd very much like to avoid manually specifying all resources if mapping works well out-of-the-box for new resources.big-architect-71258
03/03/2024, 10:03 PMworried-energy-90920
03/04/2024, 10:18 AMutils/io.go:20: provider: Failed to close: provider="proxmox@5.26.0-alpha.1709545503+9fbfb32d.dirty" error=EOF
when using a newly built provider locally (the current codebase is https://github.com/muhlba91/pulumi-proxmoxve/tree/fix/provider).
did you encounter such errors already and have a pointer?ancient-policeman-24615
03/04/2024, 10:46 AMutils/io.go
isn’t present in the bridge or pulumi/pulumi.big-architect-71258
03/04/2024, 10:49 AMworried-energy-90920
03/04/2024, 2:15 PMTF_LOG=TRACE
and -v11
and the only error i find in there is I0304 15:08:57.268944 80429 eventsink.go:86] eventSink::Error(<{%reset%}> utils/io.go:20: provider: Failed to close: provider="proxmox@5.26.0-alpha.1709547020+a3df0844.dirty" error=EOF
which is not surrounded by any other error.
in general, looking through the logs for error
i also find these but think they are probably unrelated:
I0304 15:08:44.332519 80429 eventsink.go:78] eventSink::Infoerr(<{%reset%}>I0304 15:08:44.331717 80453 main.go:305] one or more errors while discovering plugins: 3 errors occurred:
<{%reset%}>)
I0304 15:08:44.332569 80429 eventsink.go:78] eventSink::Infoerr(<{%reset%}> * unmarshaling package.json /Users/daniel/Projects/tmp/proxmoxve/node_modules/resolve/test/resolver/false_main/package.json: json: cannot unmarshal bool into Go struct field packageJSON.main of type string
<{%reset%}>)
I0304 15:08:44.332590 80429 eventsink.go:78] eventSink::Infoerr(<{%reset%}> * unmarshaling package.json /Users/daniel/Projects/tmp/proxmoxve/node_modules/resolve/test/resolver/invalid_main/package.json: json: cannot unmarshal array into Go struct field packageJSON.main of type string
<{%reset%}>)
I0304 15:08:44.332607 80429 eventsink.go:78] eventSink::Infoerr(<{%reset%}> * unmarshaling package.json /Users/daniel/Projects/tmp/proxmoxve/node_modules/resolve/test/resolver/malformed_package_json/package.json: unexpected end of JSON input
ancient-policeman-24615
03/04/2024, 2:20 PMpulumi up
to test? I don’t recall seeing these errors before.worried-energy-90920
03/04/2024, 2:27 PMpulumi up
run and the full output when run with TF_LOG
and v11
set.
the only error actually being printed without the log level increased is actually only the closed provider one.ancient-policeman-24615
03/05/2024, 2:17 PMworried-energy-90920
03/10/2024, 11:50 AM