incompatible_disallow_ctx_resolve_tools

[tjgq]

This flag disallows uses of the ctx.resolve_tools API, which is awkward to use and redundant with other existing APIs.

To migrate, replace this pattern:

tool_inputs, input_manifests = ctx.resolve_tools(tools = [ctx.attr._my_tool])
...
ctx.actions.run(
  inputs = tool_inputs + ...,
  input_manifests = input_manifests,
  ...
)

with one of

ctx.actions.run(executable = ctx.executable._my_tool, ...)

or

ctx.actions.run(tools = [ctx.executable._my_tool], ...)

When using ctx.actions.run_shell, the latter form is required. Otherwise, when using ctx.actions.run, prefer the former (i.e., if the tool in question is the executable for the action, there's no need to also pass it under tools).

Note that ctx.executable._my_tool refers solely to the executable file, but passing it to the executable or tools argument automatically includes its associated runfiles in the action inputs, as long as the tool is a direct dependency of the target calling ctx.actions.run/ctx.actions.run_shell. If you want to pass the tool around (e.g., in a returned provider) for other targets to use, you must obtain a FilesToRunProvider via ctx.attr._my_tool[DefaultInfo].files_to_run, and pass it around instead.