Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Build build images for languages that need them to avoid external build dependencies

Abierto
#437 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 7 días

Nadie ha tomado este issue todavía.

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
go, python, rust

Línea de trabajo

Start by locating the Python and Rust function builders and the build scripts they run; the issue does not name specific files or tests. Check how build images are configured and how ImageConfigs are respected when images are pulled. Done means Rust and Python build images include the required tools and dependencies, are kept up to date with Renovate, and can be pulled through users’ configured registries.

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

Descripción

enhancement
What problem are you facing?

Currently, our Python and Rust function builders run scripts in a build container that download tools and dependencies before building the function. This has two problems:

  1. It makes builds slower, since the download has to run every time (especially for folks on slower connections).
  2. It means builds have hidden external dependencies, which can be a reliability problem and also break for users in network restricted environments.
How could Crossplane help solve your problem?

We should build build images for Rust and Python that include all the tools and dependencies we need, and keep them up-to-date with renovate. We should respect ImageConfigs when pulling these images so that users in restricted environments can mirror them to their blessed registries.

Lenguaje dominante
Go
Estrellas
22
Forks
37
Merge medio
6 d 8 h
PR fusionados (30 d)
22

Preparar el entorno

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 crossplane/cli

Todos los issues de crossplane/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.