-
Notifications
You must be signed in to change notification settings - Fork 407
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
Buildozer: changing attributes in override functions of MODULE.bazel #1218
Comments
We may want to consider having a different For example, with gazelle overrides, we use That way these could be identifiable:
|
I think we want new buildozer syntax here, maybe |
Do we need new syntax? I was thinking |
That feels quite magic and ties Buildozer to an implementation detail of Bazel (canonical repository names). It also doesn't allow specifying extension tags such as |
are you suggesting something like |
Yes, exactly that, where |
Buildozer is not able to recognize the functions with
module_name
in MODULE.bazel file. Sobuildozer print //MODULE.bazel:all
would print something like:Note that the
archive_override
doesn't have name. So we can't update them from command line.We can follow the convention of Bazel to create a target
rules_proto_grpc~override
when Buildozer sees a *_override rule withmodule_name = "rules_proto_grpc"
.The text was updated successfully, but these errors were encountered: