https://pulumi.com logo
#automation-api
Title
# automation-api
a

acoustic-iron-92969

10/20/2021, 5:29 PM
hey folks, has anyone run into an error like this when trying to use the automation API with go?
Copy code
failed to run update: exit status 255\ncode: 255\nstdout: Updating (my-test):\n \n\nstderr: error: failed to discover plugin requirements: grpc: error unmarshalling request: failed to unmarshal *pulumirpc.GetRequiredPluginsRequest\n\n
looking to get a minimized example together if I can repoduce it, but wanted to check and see if anyone knows offhand when this happens
b

bored-oyster-3147

10/20/2021, 5:49 PM
just off the top of my head sanity check - make sure you're using the latest CLI version / auto-api version? I guess it's possible that a CLI version has changed the get required plugin response shape and the auto-api isn't deserializing correctly because those versions arent in sync?
a

acoustic-iron-92969

10/20/2021, 5:53 PM
yeah, both of those are v3.15.0 unfortunately. I definitely have a feeling this is something easy, because I can’t reproduce with a minimized example just yet. seems to work fine.
b

bored-oyster-3147

10/20/2021, 6:10 PM
are you by chance using a pre-built binary when it fails?
a

acoustic-iron-92969

10/20/2021, 6:12 PM
if you mean I’m compiling the go code into a binary then running it, yes. this is basically a little CLI tool I’m building that wraps pulumi for some functions
b

bored-oyster-3147

10/20/2021, 6:16 PM
I mean are you using the pulumi project settings feature where you point it at a
binary: filepath
because you are taking on the responsibility of building it ahead of time. If so, did you have it working that way previously? I know that in .NET,
GetRequiredPlugins
relies on plugin discovery, which in turn relies on pulumi having ownership over building the binary. This is because in .NET it relies on knowing which packages you brought in in order to determine versions. So in my use-cases when I am using a pre-built .NET binary, I have to manually install the plugins ahead of time because plugin discovery does not work. It is possible that the golang plugin discovery has the same or similar limitation.
a

acoustic-iron-92969

10/20/2021, 6:17 PM
hrmm, hang on. I think it may be something that I did to break this. I checked out and old branch and it seems to work. let me dive into the diff between these two
(thank you for the help btw, much appreciated)
💯 1
3 Views