feat: push tapir to Buf schema registry for each new tag #553
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
moritzzimmer
requested review from
harryherbig,
thisismana,
bobaaaaa,
saefty and
bastianpahlke
as code owners
Closed
moritzzimmer
added
📖 documentation
harryherbig
reviewed
Jul 4, 2024
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.
what
Push tapir on release to the (public) buf schema registry of tapir.
why
see https://buf.build/docs/bsr/introduction#bsr-goals for details
✅ automatic documentation, we could remove duplications for funcdoc and simplify tools, see https://buf.build/stroeer/tapir
✅ automatic generation of client SDKs for various proto/grpc versions and languages like java, TypeScript, Go, Swift and Python - we could remove our tooling around packaging and hosting SDKs
🟡 might be free (see plans), according to
buf beta priceit would cost $34.00/month for Teams plan which doesn't add much value🟡 we would need to refactor our imports in the client projects to the buf naming conventions, see examples for java and go