WIT management with multiple SDKs

[asteurer]

I'm wondering if there's a way for componentize-go to ease the friction of utilizing multiple SDKs that have their own WIT contracts. For example, the opentelemetry-wasi Go example app implements both the Spin Go SDK and the opentelemetry-wasi Go SDK, each with their own WIT contracts. The only way I was able to get the application to work was creating a custom WIT which combines the required dependencies for each SDK. This feels cumbersome, and it's not clear whether there's a better way to do this.

@dicej @calebschoepp I would be grateful for any thoughts or opinions.

[dicej]

componentize-py has a mechanism by which an SDK can include a componentize-py.toml file (example) which tells componentize-py where to find the WIT files for that SDK, which world to target (if there is more than one), and where the pre-generated bindings for that world live in the SDK. At build time, componentize-py will search the directories specified by the developer for such files, parse the WIT files, merge the worlds together (along with the world specified explicitly by the developer, if any) into a single world, and generate a component which targets that.

I imagine componentize-go could do something similar, although the exact developer experience might be different.

[asteurer]

Note to self:

SDK authors can embed the WIT files in their SDK:

package wit

import "embed"

//go:embed *
var Wit embed.FS

This can be used in combination with a Go list command:

$(go list -mod=readonly -m -f '{{.Dir}}' github.com/spinframework/spin-go-sdk/v3)/wit

I see a path where componentize-go manifests take the github.com/repo/path/to/wit and rely on the Go PATH for referencing the WIT files.