-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proto: update the mechanism for generating protos from spec repo #7269
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks pretty reasonable to me. I have a few small things, but nothing that crucial. (Mostly just quoting and formatting nonsense, because shells are pernicious)
Co-authored-by: M. J. Fromberger <fromberger@interchain.io>
# Get shortened ref of commit | ||
REF=$(curl -H "Accept: application/vnd.github.v3.sha" -qL \ | ||
"https://api.github.com/repos/tendermint/spec/commits/${VERS}" \ | ||
| cut -c -7) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably no real need to truncate the hash (though it is harmless).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see why you did that, because of the way the tarballer names its directory. ✔️
…dermint#7269) This pull request updates the `protocgen.sh` script to insert the `go_package` option to all of the downloaded proto files. A related pull request into the spec repo removes this options from the .proto files: tendermint/spec#358 This pull requests, along with the related spec PR, aim to move the creation of the `tendermintdev/docker-build-proto` container into the spec repo. This change also relies on several fixes to that container that are made in the PR into the spec repo.
This is a manual backport of the changes to how we build and run the protobuf toolchain images in Docker. The main effect here is to point to the new image from ghcr.io/tendermint/docker-proto-builder, but to make that work it is also necessary to update some of the branch pointers. This change does NOT include the changes from #7269 and #7291 to point to the proto files in the spec repo. To do that, we will need to create a branch or tag on the spec that has the released version, which does not exist in the spec history as it currently stands.
This is a manual backport of the changes to how we build and run the protobuf toolchain images in Docker. The main effect here is to point to the new image from ghcr.io/tendermint/docker-proto-builder, but to make that work it is also necessary to update some of the branch pointers. This change does NOT include the changes from #7269 and #7291 to point to the proto files in the spec repo. To do that, we will need to create a branch or tag on the spec that has the released version, which does not exist in the spec history as it currently stands.
This is a manual backport of the changes to how we build and run the protobuf toolchain images in Docker. The main effect here is to point to the new image from ghcr.io/tendermint/docker-proto-builder, but to make that work it is also necessary to update some of the branch pointers. This change does NOT include the changes from #7269 and #7291 to point to the proto files in the spec repo. To do that, we will need to create a branch or tag on the spec that has the released version, which does not exist in the spec history as it currently stands. (cherry picked from commit a97b081)
This pull request updates the
protocgen.sh
script to insert thego_package
option to all of the downloaded proto files. A related pull request into the spec repo removes this options from the .proto files: tendermint/spec#358This pull requests, along with the related spec PR, aim to move the creation of the
tendermintdev/docker-build-proto
container into the spec repo. This change also relies on several fixes to that container that are made in the PR into the spec repo.