self-hosted/teleport
self-hosted/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport synced 2024-10-20 01:03:40 +00:00
Code Issues Packages Projects Releases Wiki Activity
teleport/buf-connect-go.gen.yaml

23 lines
503 B
YAML
Raw Normal View History

Refactor prehog & teleterm protos to match project conventions (#20810) * Adjust go_package of lib/prehog Go protobufs This makes them follow the pattern set out by api/proto and proto. * Adjust go_package of lib/teleterm Go protobufs * Use single buf.gen.yaml to generate JS protos This also entailed changing the location of lib/teleterm protos and changing the value of their package specifier to match the conventions in other parts of the codebase. This is a breaking change but that is fine for Connect as the protos are used locally only and each build ships with matching protobufs. * Make web/packages/teleterm use protobufs from gen-proto-js We used to copy protobufs over to web/packages/teleterm/src/services/tshd since webapps used to be in a separate repo. This is no longer the case, so we can just make teleterm use protobufs from gen-proto-js. * Move prehog & teleterm protos into proto/teleport/lib * Generate JS protos to gen/proto/js * Move lib/teleterm Go protobufs to gen/proto/go * Move lib/prehog Go protobufs to gen/proto/go * Rename lib/teleterm proto package * Re-enable linter rules for teleterm & prehog * Update prehogv1 path in usagereporter_test.go * Use except instead of ignore_only to allow Google API-style responses * Add UNARY_RPC to api/proto & proto * Ignore gen/ when running addlicense * buf-js.gen.yaml: Remove comment about lack of go_package for JS * Move prehog protos to proto/prehog/v1alpha * Adjust prehog's go_package to match proto package
2023-02-03 14:47:06 +00:00
version: v1
Tweak protogen to not change protos from cloud (#24688) * Tweak protogen to not change protos from cloud * Use strategy: all whenever possible
2023-04-18 14:22:12 +00:00
managed:
enabled: true
go_package_prefix:
default: github.com/gravitational/teleport/gen/proto/go
Refactor prehog & teleterm protos to match project conventions (#20810) * Adjust go_package of lib/prehog Go protobufs This makes them follow the pattern set out by api/proto and proto. * Adjust go_package of lib/teleterm Go protobufs * Use single buf.gen.yaml to generate JS protos This also entailed changing the location of lib/teleterm protos and changing the value of their package specifier to match the conventions in other parts of the codebase. This is a breaking change but that is fine for Connect as the protos are used locally only and each build ships with matching protobufs. * Make web/packages/teleterm use protobufs from gen-proto-js We used to copy protobufs over to web/packages/teleterm/src/services/tshd since webapps used to be in a separate repo. This is no longer the case, so we can just make teleterm use protobufs from gen-proto-js. * Move prehog & teleterm protos into proto/teleport/lib * Generate JS protos to gen/proto/js * Move lib/teleterm Go protobufs to gen/proto/go * Move lib/prehog Go protobufs to gen/proto/go * Rename lib/teleterm proto package * Re-enable linter rules for teleterm & prehog * Update prehogv1 path in usagereporter_test.go * Use except instead of ignore_only to allow Google API-style responses * Add UNARY_RPC to api/proto & proto * Ignore gen/ when running addlicense * buf-js.gen.yaml: Remove comment about lack of go_package for JS * Move prehog protos to proto/prehog/v1alpha * Adjust prehog's go_package to match proto package
2023-02-03 14:47:06 +00:00
plugins:
- name: go
Tweak protogen to not change protos from cloud (#24688) * Tweak protogen to not change protos from cloud * Use strategy: all whenever possible
2023-04-18 14:22:12 +00:00
strategy: all
Fix package names for v1 protos, misc proto changes (#24183) * Delete teleterm's ptyHost/v1, added by mistake * Add package name to protos conforming to PACKAGE_VERSION_SUFFIX * use go run in buf-connect-go.gen.yaml directly * Run protogen in place * Run the buf-go generation off of go run This also adds protoc-gen-go-grpc to go.mod
2023-04-06 22:53:31 +00:00
path:
- go
- run
- google.golang.org/protobuf/cmd/protoc-gen-go
Refactor prehog & teleterm protos to match project conventions (#20810) * Adjust go_package of lib/prehog Go protobufs This makes them follow the pattern set out by api/proto and proto. * Adjust go_package of lib/teleterm Go protobufs * Use single buf.gen.yaml to generate JS protos This also entailed changing the location of lib/teleterm protos and changing the value of their package specifier to match the conventions in other parts of the codebase. This is a breaking change but that is fine for Connect as the protos are used locally only and each build ships with matching protobufs. * Make web/packages/teleterm use protobufs from gen-proto-js We used to copy protobufs over to web/packages/teleterm/src/services/tshd since webapps used to be in a separate repo. This is no longer the case, so we can just make teleterm use protobufs from gen-proto-js. * Move prehog & teleterm protos into proto/teleport/lib * Generate JS protos to gen/proto/js * Move lib/teleterm Go protobufs to gen/proto/go * Move lib/prehog Go protobufs to gen/proto/go * Rename lib/teleterm proto package * Re-enable linter rules for teleterm & prehog * Update prehogv1 path in usagereporter_test.go * Use except instead of ignore_only to allow Google API-style responses * Add UNARY_RPC to api/proto & proto * Ignore gen/ when running addlicense * buf-js.gen.yaml: Remove comment about lack of go_package for JS * Move prehog protos to proto/prehog/v1alpha * Adjust prehog's go_package to match proto package
2023-02-03 14:47:06 +00:00
out: .
Fix package names for v1 protos, misc proto changes (#24183) * Delete teleterm's ptyHost/v1, added by mistake * Add package name to protos conforming to PACKAGE_VERSION_SUFFIX * use go run in buf-connect-go.gen.yaml directly * Run protogen in place * Run the buf-go generation off of go run This also adds protoc-gen-go-grpc to go.mod
2023-04-06 22:53:31 +00:00
opt: module=github.com/gravitational/teleport
Refactor prehog & teleterm protos to match project conventions (#20810) * Adjust go_package of lib/prehog Go protobufs This makes them follow the pattern set out by api/proto and proto. * Adjust go_package of lib/teleterm Go protobufs * Use single buf.gen.yaml to generate JS protos This also entailed changing the location of lib/teleterm protos and changing the value of their package specifier to match the conventions in other parts of the codebase. This is a breaking change but that is fine for Connect as the protos are used locally only and each build ships with matching protobufs. * Make web/packages/teleterm use protobufs from gen-proto-js We used to copy protobufs over to web/packages/teleterm/src/services/tshd since webapps used to be in a separate repo. This is no longer the case, so we can just make teleterm use protobufs from gen-proto-js. * Move prehog & teleterm protos into proto/teleport/lib * Generate JS protos to gen/proto/js * Move lib/teleterm Go protobufs to gen/proto/go * Move lib/prehog Go protobufs to gen/proto/go * Rename lib/teleterm proto package * Re-enable linter rules for teleterm & prehog * Update prehogv1 path in usagereporter_test.go * Use except instead of ignore_only to allow Google API-style responses * Add UNARY_RPC to api/proto & proto * Ignore gen/ when running addlicense * buf-js.gen.yaml: Remove comment about lack of go_package for JS * Move prehog protos to proto/prehog/v1alpha * Adjust prehog's go_package to match proto package
2023-02-03 14:47:06 +00:00
- name: connect-go
Tweak protogen to not change protos from cloud (#24688) * Tweak protogen to not change protos from cloud * Use strategy: all whenever possible
2023-04-18 14:22:12 +00:00
strategy: all
Fix package names for v1 protos, misc proto changes (#24183) * Delete teleterm's ptyHost/v1, added by mistake * Add package name to protos conforming to PACKAGE_VERSION_SUFFIX * use go run in buf-connect-go.gen.yaml directly * Run protogen in place * Run the buf-go generation off of go run This also adds protoc-gen-go-grpc to go.mod
2023-04-06 22:53:31 +00:00
path:
- go
- run
- github.com/bufbuild/connect-go/cmd/protoc-gen-connect-go
Refactor prehog & teleterm protos to match project conventions (#20810) * Adjust go_package of lib/prehog Go protobufs This makes them follow the pattern set out by api/proto and proto. * Adjust go_package of lib/teleterm Go protobufs * Use single buf.gen.yaml to generate JS protos This also entailed changing the location of lib/teleterm protos and changing the value of their package specifier to match the conventions in other parts of the codebase. This is a breaking change but that is fine for Connect as the protos are used locally only and each build ships with matching protobufs. * Make web/packages/teleterm use protobufs from gen-proto-js We used to copy protobufs over to web/packages/teleterm/src/services/tshd since webapps used to be in a separate repo. This is no longer the case, so we can just make teleterm use protobufs from gen-proto-js. * Move prehog & teleterm protos into proto/teleport/lib * Generate JS protos to gen/proto/js * Move lib/teleterm Go protobufs to gen/proto/go * Move lib/prehog Go protobufs to gen/proto/go * Rename lib/teleterm proto package * Re-enable linter rules for teleterm & prehog * Update prehogv1 path in usagereporter_test.go * Use except instead of ignore_only to allow Google API-style responses * Add UNARY_RPC to api/proto & proto * Ignore gen/ when running addlicense * buf-js.gen.yaml: Remove comment about lack of go_package for JS * Move prehog protos to proto/prehog/v1alpha * Adjust prehog's go_package to match proto package
2023-02-03 14:47:06 +00:00
out: .
Fix package names for v1 protos, misc proto changes (#24183) * Delete teleterm's ptyHost/v1, added by mistake * Add package name to protos conforming to PACKAGE_VERSION_SUFFIX * use go run in buf-connect-go.gen.yaml directly * Run protogen in place * Run the buf-go generation off of go run This also adds protoc-gen-go-grpc to go.mod
2023-04-06 22:53:31 +00:00
opt: module=github.com/gravitational/teleport
Reference in a new issue Copy permalink