A unique name for this target.

The target executable to wrap. This is the actual program that will be executed.

The entrypoint's runfiles path will be automatically resolved at runtime through the Bazel
runfiles mechanism. This must be an executable target (e.g., a binary, a script, or another
launcher_binary).

Example: entrypoint = "@python_3_11//:python" or entrypoint = "//tools:my_tool"

Arguments to embed in the binary that will be passed to the entrypoint.

These arguments are baked into the binary at build time. They support Bazel location
expansion (e.g., $(rlocationpath), $(location), $(execpath)).

Arguments matching the pattern $(rlocationpath ...) are automatically detected and marked
for runtime path transformation unless you explicitly set transformed_args.

Example:

embedded_args = [
    "--config",
    "$(rlocationpath :config.yaml)",  # Auto-detected for transformation
    "--mode=production",               # Literal string, not transformed
]

Explicit list of argument indices that need runtime runfiles path transformation.

Index 0 is the entrypoint, index 1 is the first embedded arg, index 2 is the second, etc.

Default behavior (empty list):

• Entrypoint (index 0) is always transformed
• Any argument matching $(rlocationpath ...) is transformed
• Other arguments are passed as literal strings

Custom behavior:
Set explicit indices to transform:

transformed_args = [0, 2, 5]  # Transform entrypoint, 2nd arg, and 5th arg

Disable all transformation:

transformed_args = [-1]  # Special value: no transformation at all

Use this when you want fine-grained control over which paths are resolved through runfiles.

Runtime dependencies (data files, scripts, etc.) needed by the entrypoint.

These files and their transitive runfiles will be included in the binary's runfiles tree,
making them available at runtime. Use $(rlocationpath) to reference these files in
embedded_args.

Example:

data = [
    ":config.yaml",
    "//data:test_fixtures",
    "@some_external//:data_files",
]