[enhancement] github runner: support just-in-time (JIT) runner configuration

Abierto
#957 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

@atishay-kasliwal ya está trabajando en esto.

Desde el 16/11/2026.

  • #971 de @atishay-kasliwal — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, azure, github-actions, go
Área
cli, cloud, security

Línea de trabajo

Read the self-hosted runner documentation linked in the issue and trace the --install-ghactions-runner CLI options and the code that generates runner user data. Check how existing token, App and PAT options are validated and how runner startup differs across platforms. Done means the JIT config file option starts a one-job ephemeral runner, conflicting options return an error, and registration tokens do not appear in user data or Pulumi state.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

Reading https://github.com/redhat-developer/mapt/blob/main/docs/self-hosted-runner.md, the GitHub runner is registered with a registration token written into the instance's cloud-init user data (config.sh --token … --replace). That token is valid for one hour and isn't bound to one runner. Any process on the host can read it from the instance metadata service, and so can anyone with access to the cloud account or the Pulumi state. Within the hour, they can register other runners on the same repository or organization, with any name and labels, or replace an existing runner of the same name.

This matters when the jobs on the runner aren't fully trusted, or when the cloud account and the GitHub organization belong to different parties.

Proposal

Support GitHub's just-in-time (JIT) runners (REST API, security hardening guide). A JIT config registers exactly one ephemeral runner, whose name, labels and runner group are set by whoever generated it. It can't register another runner, and it's useless once consumed.

  1. Add --ghactions-runner-jitconfig-file <path>: a JIT config generated by the caller, read from a file so it stays out of process listings. It excludes the token, App and PAT options, and --ghactions-runner-labels / --ghactions-runner-ephemeral (the config sets them).
  2. With it, the snippets start the runner with run.sh --jitconfig <config> instead of config.sh, on every platform.
  3. Optionally, with --ghactions-app-*, mapt generates a JIT config itself instead of a registration token, so App users get the same benefit.

Related: #851.

Acceptance
  • mapt aws rhel create --install-ghactions-runner --ghactions-runner-jitconfig-file jit.txt … brings up a runner that takes one job and is then removed by GitHub.
  • No registration token appears in the user data or the Pulumi state.
  • Combining the option with a token, App or PAT option exits with an error.
Lenguaje dominante
Go
Estrellas
25
Forks
41
Merge medio
5 d 3 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de redhat-developer/mapt

Todos los issues de redhat-developer/mapt

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.