load("@prelude//platforms:defs.bzl", "host_configuration")
load(":defs.bzl", "execution_platform")

# Where every action runs: locally, against the BuildBuddy cache. The same
# arrangement jolt-native uses, and registered the same two ways — `[build]
# execution_platforms` in .buckconfig and `[parser] target_platform_detector_spec`
# there too, since setting only the first leaves toolchain-owned actions on the
# prelude's uncached default.
execution_platform(
    name = "cache",
    cpu_configuration = host_configuration.cpu,
    os_configuration = host_configuration.os,
    use_windows_path_separators = host_info().os.is_windows,
    visibility = ["PUBLIC"],
)

# The same platform, allowed to dispatch. Most of this graph cannot use it: the
# packaging steps name an Android SDK, a Chez cross build and an OpenSSL by
# absolute path, and a worker has none of them. The boot image compile is the
# one that could, which is why jolt reaches it through a manifest rather than a
# path — see android/BUCK.
execution_platform(
    name = "remote",
    cpu_configuration = host_configuration.cpu,
    os_configuration = host_configuration.os,
    remote_enabled = True,
    remote_execution_properties = {
        "OSFamily": "Linux",
        "container-image": "docker://gcr.io/flame-public/rbe-ubuntu24-04:latest",
    },
    use_windows_path_separators = host_info().os.is_windows,
    visibility = ["PUBLIC"],
)