Skip to content
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

[v10] Refactor teleterm protos to match project conventions #21451

Merged
merged 3 commits into from
Feb 9, 2023

Conversation

ravicious
Copy link
Member

Backport #20810.

The small twist here is that instead of actually backporting the commit #20810 merged into master, I backported the v11 backport instead #21394. v11 and v10 have much more things in common than current master and v12 so I figured it'd be easier to deal with merge conflicts this way.


  • Moved teleterm's proto files from their respective lib/ dir to proto/.
  • Updated go_package of lib/teleterm protobufs to match conventions used by api/proto and proto.
    • lib/teleterm/api/protogen/golang/v1 before
    • gen/proto/go/teleport/lib/teleterm/v1/ now
    • proto package name has been updated to match the new location.
  • JS protobufs for now live in gen/proto/js in the root folder.
  • Connect no longer needs to copy protobufs to its own directory.
    • Instead it uses protobufs from gen/proto/js so that any change done through make grpc is automatically picked up by Connect.

* Moved teleterm's proto files from their respective `lib/` dir to `proto/`.
* Updated `go_package` of `lib/teleterm` protobufs to match conventions
  used by `api/proto` and `proto`.
  * `lib/teleterm/api/protogen/golang/v1` before
  * `gen/proto/go/teleport/lib/teleterm/v1/` now
  * proto package name has been updated to match the new location.
* JS protobufs for now live in `gen/proto/js` in the root folder.
* Connect no longer needs to copy protobufs to its own directory.
   * Instead it uses protobufs from `gen/proto/js` so that any change
     done through `make grpc` is automatically picked up by Connect.
@ravicious
Copy link
Member Author

ravicious commented Feb 8, 2023

The teleport-operator fix (#21362) is not included because v10 doesn't have lib/services/usagereporter.go. I did a tag build and teleport-operator was built without problems.

@ravicious ravicious marked this pull request as ready for review February 8, 2023 12:17
Copy link
Contributor

@codingllama codingllama left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from gzdunek February 8, 2023 16:50
@ravicious ravicious enabled auto-merge (squash) February 9, 2023 07:42
@ravicious ravicious merged commit 307c377 into branch/v10 Feb 9, 2023
@ravicious ravicious deleted the ravicious/v10/backport-20810-grpc-refactor branch February 9, 2023 13:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants