Sync rekor-tiles protos into protobuf-specs#661
Conversation
|
Looks like typescript would need an import of "bufbuild/wire", this is only a problem because we're also sync'ing in the service definition. I can "exclude" that from the sync. |
if the issue is that you didn't want to poke the custom rust codegen code, I can give it a try (no promises on results though) |
I took a quick look, and decided someone else maybe would want to. I don't think it's very complicated, was just worried I was gonna burn a bunch of hours |
|
Two commits for rust in https://github.com/jku/protobuf-specs/commits/sync-rekor-tiles/ if you want them (first is the codegen change, second is "make rust" result) (I can make a separate PR as well, let me know) |
- sync is by manually running service-protos/sync-rekor-tiles.sh - pull in latest tag (it doesn't do releases) from rekor-tiles - rewrite the go_package to match protobuf specs - ignore protos for grpc service defintions - do NOT put service protos in ./protos because we export those in the service-builder container image - rework language builder to include ./service-protos - include ./service-protos in exported jar - remove jsonschema TODO: - handle rust code gen in the rust codebase? Signed-off-by: Appu Goundan <appu@google.com>
bc4bcd8 to
1c55db8
Compare
|
oh woops, I updated, amended and force pushed. I'll cherry pick in your diffs |
Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
Hayden-IO
left a comment
There was a problem hiding this comment.
Great work on this!
Do you want to add a nightly GHA that tracks when there are new tags and changes to the protos in all services?
Makefile
Outdated
| ${DOCKER_RUN} -v ${PWD}:/defs ${PROTOC_RUBY_IMAGE} ${PROTO_INCLUDES}\ | ||
| --ruby_out=/defs/gen/pb-ruby/lib ${PROTOS} | ||
|
|
||
| # TODO: serivce-proto code gen for rust |
I can add it in a followup, this is already kind of a hefty PR. |
Signed-off-by: Appu Goundan <appu@google.com>
ed0752a to
6a8402f
Compare
gen/pb-ruby/lib/rekor_service_pb.rb
Outdated
There was a problem hiding this comment.
Is this supposed to be here, or is this leftover from a generation with the service proto?
There was a problem hiding this comment.
Maybe try a make clean; make all to confirm?
There was a problem hiding this comment.
I thought I did, weird.
There was a problem hiding this comment.
gotta update the makefile
There was a problem hiding this comment.
I think there are some other ruby things in there that might need updating: https://github.com/sigstore/protobuf-specs/blob/main/gen/pb-ruby/lib/sigstore_protobuf_specs.rb
There was a problem hiding this comment.
we're not using the generated protos from this repo since they depend on the protobuf gem
Signed-off-by: Appu Goundan <appu@google.com>
|
it looks like typescript needs an update too, to: https://github.com/sigstore/protobuf-specs/blob/main/gen/pb-typescript/src/index.ts @bdehamer ? |
|
Should I add TODOs/issues for typescript and ruby? |
|
What's the current issue(s)? Given we aren't immediately targeting JS/Ruby Rekor v2 support, filing issues for now would be fine. Should we omit js/ruby entirely if there are issues? |
jku
left a comment
There was a problem hiding this comment.
leaving further ts and ruby changes to issues seems fine, let's just ping the relevant folks
service-protos/sync-rekor-tiles.sh
Outdated
| git clone --filter=blob:none --no-checkout --depth=1 https://github.com/sigstore/rekor-tiles.git ./rekor-tiles && \ | ||
| cd ./rekor-tiles && \ | ||
| git sparse-checkout set --no-cone '/api/proto/rekor/v2/*.proto' '!**/rekor_service.proto' && \ | ||
| git fetch origin tag "$latest_tag" --no-tags && \ | ||
| git checkout "$latest_tag" && \ | ||
| cd ../ && \ | ||
| cp -R ./rekor-tiles/api/proto/* . && \ | ||
| rm -rf ./rekor-tiles |
There was a problem hiding this comment.
was there a reason to use "&&" here? You use errexit already so it shouldn't be needed
There was a problem hiding this comment.
No. Started with a script from somewhere else and continued with that style. It's unnecessary, I wasnt thinking.
|
This is just a note, not suggesting any changes:
I thought this would have no affect on the sigstore-python PR but it turns out we did actually use CreateEntryRequest from the service protos to build the request message. Doing that manually is not an issue. |
Oh I didn't think about that. Hrmmm.. seems silly to not include it. |
Signed-off-by: Appu Goundan <appu@google.com>
|
okay cleaned up the script a bit |
|
oh shoot, jku contributed to this PR so need another review. |
Hayden-IO
left a comment
There was a problem hiding this comment.
@loosebazooka does this need to be rerun with the new tag or is this generated from a fix locally?
|
Will merge, and rerun with updates on a new tag |
|
Open #669 to expose these new types as part of the generated npm package. |
Summary
Release Note
Documentation