-
Notifications
You must be signed in to change notification settings - Fork 18
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
build image rule #43
Comments
Could you elaborate a bit more how such a rule will work? Like how do you expect dependencies to be resolved? |
if I can use the lint test as follows:
I would like to be able to have the ability to create image with the same ease:
|
Hey! In you example the target |
@srikrsna-buf How this relates to having a buf image? |
Images are an extension of file descriptor sets. In the example that you proposed they are more or less the same. The one missing piece is the module info which will have information of the module this belongs to. We have an unreleased push rule perhaps you are looking for something similar that builds the image? |
I am looking for rule that can generate the file that I can store and later pass to the buf-breaking-test as against argument. |
If it is a rule then it will always build from the same source as |
I am not going to use the result for the rule form the current version, I am going to use the output of the rule to store in location from where I can pull it for the next execution |
Okay, sounds good so you need a rule that builds the image for all you proto files as a single module, I think it will look similar to the push rule that I linked. |
yes, that will be great |
I'm looking for such a rule as well for the exact same reason. Any update on if we can get that and if so when? |
We are in the midst of some change to how build works, waiting for them to land before we add this rule. |
I think having a bazel rule that can create the buf image for a target is going to be extremely useful. Without it, I have to repeat all the bazel config in order to build the image.
The text was updated successfully, but these errors were encountered: