mirror of https://github.com/pulumi/pulumi.git
4a12902bde
A few weeks ago we added the concept of package references, mostly for parametrised providers so that we wouldn't have to send the parameter value over and over for each `RegisterResourceRequest`. This was done by sending the package reference through the `provider` field. Nothing yet uses this feature (it hasn't yet been added to any language SDKs), and thinking over this the last week I realised there was an issue using this for extension packages. When using an extension provider it's valid to also specify an explicit provider, which will be using the `provider` field. At this point there's no where for the SDK to send extra information to the engine about the parameterisation. This is a small reworking of this idea to use a separate `package` field, so that even for an extension type we can specify the parameterised package it comes from and an explicit provider for it. |
||
|---|---|---|
| .. | ||
| codegen | ||
| testing | ||
| alias.pb.go | ||
| analyzer.pb.go | ||
| analyzer_grpc.pb.go | ||
| callback.pb.go | ||
| callback_grpc.pb.go | ||
| converter.pb.go | ||
| converter_grpc.pb.go | ||
| engine.pb.go | ||
| engine_grpc.pb.go | ||
| errors.pb.go | ||
| language.pb.go | ||
| language_grpc.pb.go | ||
| plugin.pb.go | ||
| provider.pb.go | ||
| provider_grpc.pb.go | ||
| resource.pb.go | ||
| resource_grpc.pb.go | ||
| source.pb.go | ||