Extend the buf registry sdk command to reverse versions into module and reference

[KenxinKun]

Feature

Today we can do:

$ buf registry sdk version --module=buf.build/connectrpc/eliza --plugin=buf.build/protocolbuffers/go
v1.33.0-20230913231627-233fca715f49.1

However we cannot do the reverse operation.

I am presented with the challenge that I want to use buf export for all the Go imports from the BSR in my go.mod file, for example:

go 1.23.0

require (
	buf.build/gen/go/acme/paymentapis/protocolbuffers/go v1.35.2-20220907172603-9a877cf260e1.1
)

I tried doing buf export buf.build/acme/paymentapis:main -o ./temp and it works with the latest, however if I try
buf export buf.build/acme/paymentapis:9a877cf260e1 -o ./temp with the short sha it fails with resource not found.

Is there a way to get exactly the version in the go.mod?

[doriable]

I discussed this proposal and the point brought up about resolving a short SHA for buf commands.
We unfortunately do not have the bandwidth right now to pursue either of these options, however, I might be able to provide some workarounds that can help with this.

If you are already able to parse the SDK name from buf.build/gen/go/acme/paymentapis/protocolbuffers/go v1.35.2-20220907172603-9a877cf260e1.1 to the module buf.build/acme/paymentapis with the short SHA for the commit 9a877cf260e1, you can use buf registry module commit to query for the commit.

For example, the following provides a list of the commits on buf.build/acme/paymentapis that I then piped into jq, and this list can be used to find the commit with the prefix 9a877cf260e1:

$ buf registry module commit list buf.build/acme/paymentapis --format json | jq .commits.[]?.commit
"9a877cf260e1488d869a31fce3bea26d"
"2675d6a595ac4e0fb45cedc62edfc611"

Let me know if this workaround can help at least unblock you and if you have any other questions.