Bazelify pomerium #4117
Draft
Bazelify pomerium #4117
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Somewhat a POC to migrate Pomerium to using bazel. I managed to get
bazel build //...,bazel run //cmd/pomerium:pomeriumandbazel test //...to work (minus some test failures). The main goal here was to support a better path forward for providing multi-lingual proto libraries to hopefully make the enterprise-client easier to adapt to any language that supports protobuf.User Explanation
Checklist
improvement/bug/ etc)I'm publishing this as a draft PR to support discussion, I have not spent time cleaning up code which is needed. This was mostly created using gazelle, however some manual modification to library versions and some patches were need to get the build to work.