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

api: build using buf #3368

Merged
merged 1 commit into from
Feb 14, 2025
Merged

api: build using buf #3368

merged 1 commit into from
Feb 14, 2025

Conversation

will-isovalent
Copy link
Contributor

@will-isovalent will-isovalent commented Feb 5, 2025

Refactor our build pipeline for the protobuf API to use buf1 to do our code generation.

This approach has a few key advantages:

  1. Simpler and more maintainable. We no longer need to maintain a complex makefile that
    gets more complex with every new .proto file.

  2. Automatic checking for API breakages including JSON and wire compatibility.

  3. Linting and automatic code formatting to improve code consistency and enforce best
    practices. Note: linting is currently disabled pending a larger incoming PR that will
    address current issues.

@will-isovalent will-isovalent force-pushed the pr/will/buf branch 7 times, most recently from c0761af to a7eaa87 Compare February 12, 2025 16:00
Copy link

netlify bot commented Feb 12, 2025

Deploy Preview for tetragon ready!

Name Link
🔨 Latest commit b398807
🔍 Latest deploy log https://app.netlify.com/sites/tetragon/deploys/67af77b3bff8b80008a6716b
😎 Deploy Preview https://deploy-preview-3368--tetragon.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@will-isovalent will-isovalent force-pushed the pr/will/buf branch 3 times, most recently from 61ab652 to 3760d67 Compare February 12, 2025 21:07
@will-isovalent will-isovalent added the release-note/misc This PR makes changes that have no direct user impact. label Feb 12, 2025
@will-isovalent will-isovalent force-pushed the pr/will/buf branch 6 times, most recently from dd38012 to de32010 Compare February 13, 2025 16:19
@will-isovalent will-isovalent marked this pull request as ready for review February 13, 2025 16:20
@will-isovalent will-isovalent requested a review from a team as a code owner February 13, 2025 16:20
@michi-covalent michi-covalent self-requested a review February 13, 2025 16:54
@will-isovalent will-isovalent removed the request for review from olsajiri February 13, 2025 17:04
Copy link
Contributor

@michi-covalent michi-covalent left a comment

Choose a reason for hiding this comment

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

Refactor our build pipeline for the protobuf API to use buf[1] to do our code generation.

This approach has a few key advantages:

1. Simpler and more maintainable. We no longer need to maintain a complex makefile that
   gets more complex with every new .proto file.

2. Automatic checking for API breakages including JSON and wire compatibility.

3. Linting and automatic code formatting to improve code consistency and enforce best
   practices. Note: linting is currently disabled pending a larger incoming PR that will
   address current issues.

[1]: https://buf.build/docs/cli/

Signed-off-by: William Findlay <william.findlay@isovalent.com>
@will-isovalent will-isovalent merged commit eea39fd into main Feb 14, 2025
48 checks passed
@will-isovalent will-isovalent deleted the pr/will/buf branch February 14, 2025 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants