pulumi/proto
Fraser Waters 920e928886 Fix the go_package option on the .proto files
This doesn't really effect anything with our current usage, but if we
ever put proto files in another package and try to import the current
set it wouldn't actually be able to find them.

I noticed this while working on
https://github.com/pulumi/pulumi/pull/10792 where I added a new
"pulumirpc.engine" package. The proto file could refer to things like
"pulumirpc.PluginDependency" but the go code then tried to import it
like `_go "github.com/pulumi/pulumi/v3/proto/go/pulumirpc"` which isn't
actually the correct import path (missing the sdk folder part, and there
isn't acutally a folder called pulumirpc).
2022-09-20 09:31:03 +01:00
..
build-container Compile protobufs with "pulumi" namespace (#10074) 2022-07-12 14:45:03 +01:00
google/protobuf Compile protobufs with "pulumi" namespace (#10074) 2022-07-12 14:45:03 +01:00
pulumi Fix the go_package option on the .proto files 2022-09-20 09:31:03 +01:00
.checksum.txt Fix the go_package option on the .proto files 2022-09-20 09:31:03 +01:00
generate.sh Fix docker in sdk/proto/generate.sh on M1 (#10099) 2022-07-12 19:57:01 +02:00
grpc_version.txt Add getOrganization to nodejs and python (#10504) 2022-08-31 10:33:29 +01:00