name: setup-buildx
description: |
  Wrapper around docker/setup-buildx-action that defaults to the buildkit
  service in the caller's own namespace. Lets workflow authors skip the
  boilerplate of pointing setup-buildx at a remote driver.

inputs:
  endpoint:
    # A BARE Service name, deliberately, rather than an FQDN. A job container
    # resolves it in its own namespace, which is where its runner's buildkit
    # lives on every cluster here: `gitea` on aceofbase, `gitea-runner` on
    # planet-express. One default is therefore correct on both, and stays
    # correct for a cluster nobody has built yet.
    #
    # It used to default to `tcp://buildkit.gitea.svc.cluster.local:1234`,
    # which named aceofbase's namespace explicitly. That resolved to nothing
    # from planet-express, so every workflow moved there had to override it —
    # and the failure mode was a DNS error inside buildx rather than anything
    # naming this action.
    description: 'BuildKit TCP endpoint. Defaults to the buildkit Service in the calling job''s own namespace.'
    required: false
    default: 'tcp://buildkit:1234'
  version:
    description: 'buildx version to install (passed through).'
    required: false
    default: 'latest'

runs:
  using: composite
  steps:
    - uses: docker/setup-buildx-action@v3
      with:
        driver: remote
        endpoint: ${{ inputs.endpoint }}
        version: ${{ inputs.version }}