Convert legacy.federation.v1beta1, module.v1beta1 to module.v1beta1, module.v1 #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR does a bunch of moves and updates:
buf.registry.module.v1beta1
tobuf.registry.module.v1
.buf.registry.legacy.federation.v1beta1
tobuf.registry.module.v1beta1
.buf.registry.legacy.federation.v1beta1
into the newbuf.registry.module.v1beta1
.buf.registry.owner.v1beta1
tobuf.registry.owner.v1
.The rest of the updates are referenced in terms of their new package location, not old package location:
registry
fromv1beta1.ResourceRef
, instead creating a wrapperGetGraphRequest.ResourceRef
message that contains aregistry
field. We only need/wantregistry
to be added toResourceRef
for this specific RPC.v1_buf_yaml_file, v1_buf_lock_file
from bothv1beta1
andv1
UploadRequests
.digest_type
for allv1
RPC request messages.DIGEST_TYPE_B4
inv1
.v1_buf_yaml_file, v1_buf_lock_file
fromv1
DownloadResponse
.required
market forv1_buf_yaml_file
fromv1beta1
DownloadResponse
.The result is a
v1beta1
module API that allows for federation and B4 digests, and a cleaned-upv1
module API that only has what we need going forward.Replaces #73.