Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Deployable facets: Dockerfile ENTRYPOINT/CMD, CronJob schedules, Ingress hosts, Azure Pipelines

Aperta
  • Qualcosa non va?
#162 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
azure, dockerfile, kubernetes
Ambito
ci-cd, devops, infrastructure

Direzione di ricerca

Read the scope and acceptance criteria in #11, then inspect the existing deployable detection and evidence handling. Update tests/map_corpus/golden_expectations.json with expectations for Dockerfile literals, CronJob schedules, Ingress hosts and paths, and Azure Pipelines. Done means all four facets are detected with source evidence while expressions and templates remain unresolved.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement follow-up

Release scope update (1.1.0)

Docker launch declarations and CronJob schedule facets are tracked by #184. Ingress hosts/paths and Azure Pipelines remain follow-up work in this parent.

Deployable facets: Dockerfile ENTRYPOINT/CMD, CronJob schedules, Ingress hosts, Azure Pipelines

Background

Issue #11 was scoped at 1.0 to identify CI workflow relationships and infrastructure definitions. On main, GitHub Actions, GitLab CI, Dockerfiles, Compose services, Terraform modules, Helm charts, and Kubernetes manifests (workloads, resources) are detected. Four specific facets promised in the 1.0-scope comment are missing.

What 1.0 ships

  • GitHub Actions, GitLab CI, Jenkins workflows as deployable nodes.
  • Dockerfiles as container_build deployables linked to source components.
  • Docker Compose services as service deployables with depends_on edges.
  • Terraform modules, Helm charts, Kubernetes workloads and generic resources.
  • SAM Lambda functions.
  • Golden corpus: deployables precision 1.00, recall 1.00 (40 TP, 0 FP, 0 FN).

Remaining work (acceptance criteria from #11)

The following facets were promised in the 1.0-scope comment and were confirmed absent by audit:

  • Dockerfile ENTRYPOINT/CMD literals: Emit these as interface properties on a container_build deployable node, with evidence. A Dockerfile is detected as a deployable but its ENTRYPOINT/CMD content is not extracted.
  • Kubernetes CronJob schedules: A CronJob currently appears as a plain workload node. Emit the cron schedule expression as a facet, and consider a distinct kind or subkind.
  • Kubernetes Ingress hosts and paths: An Ingress currently appears as a generic resource. Emit declared hosts and path prefixes as interface nodes or facets with evidence.
  • Azure Pipelines: No Azure Pipelines definition is detected. Emit azure-pipelines.yml as a ci_workflow deployable, consistent with the GitHub Actions treatment.

Each must attach evidence (source path, line range, parser version). Expressions, computed values, and templated paths must be preserved as unresolved rather than evaluated.

Links

  • #11 (1.0.0 issue being closed)
  • #48 (GitHub Actions working directories — closed, related)
  • tests/map_corpus/golden_expectations.json (add deployable facet expectations)
Lingua principale
Go
Stelle
0
Fork
0
Merge medio
5h 8m
PR unite (30g)
54

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di war-and-code/dircue

Tutte le issue di war-and-code/dircue

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.