adorsys / adorsys/status-list-server
Separate Helm and templating checks into a dedicated workflow
- Linguagem predominante
- Rust
- Estrelas
- 22
- Forks
- 5
- Merge médio
- 2d 6h
- PRs com merge (30d)
- 47
Descrição
## Objective
Extract all Helm chart rendering, linting, and Kubernetes templating validation checks from `.github/workflows/CI.yml` into a dedicated `.github/workflows/helm-checks.yml` workflow.
## Context
`.github/workflows/CI.yml` has grown to nearly 1,000 lines. In addition to core Rust compilation, formatting, clippy, unit tests, and security audits, it executes several Helm-related jobs (`helm-lint`, `helm-template-local`, `kube-linter`, `prometheus-alert-rules-lint`). This mixes concerns, clutters CI logs, and slows down feedback loops for pure Rust code changes.
## Deliverables
- [ ] Create `.github/workflows/helm-checks.yml` that triggers on pull requests and pushes touching `helm/**` or `.github/workflows/helm-checks.yml`.
- [ ] Migrate all helm jobs/actions to `helm-checks.yml`.
- [ ] Keep `CI.yml` focused strictly on the Rust crate lifecycle (check, clippy, tests, coverage, audit, security).
- [ ] Update branch protection rules and documentation where status check names change.
## Acceptance Criteria
- [ ] `CI.yml` is significantly leaner and free of Helm templating logic.
- [ ] Helm template validation runs reliably in its own dedicated workflow when Helm files are modified.
- [ ] CI pipeline execution time for Rust PRs is improved.
Guia de contribuição
Direção de pesquisa
Start by reading `.github/workflows/CI.yml` and locating the `helm-lint`, `helm-template-local`, `kube-linter`, and `prometheus-alert-rules-lint` jobs. Copy/move those to a new `.github/workflows/helm-checks.yml`, then set triggers for pull requests and pushes affecting `helm/**` or `.github/workflows/helm-checks.yml`. Remove Helm logic from CI.yml so it stays Rust-focused, and update any docs or branch-protection references to the renamed checks. Done when Rust-only PRs no longer run Helm jobs and Helm-related changes run in helm-checks.yml with matching status check names.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- github-actions, helm
- Domínio
- ci-cd
- Tipo de issue
- Refatoração
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Ativa
- Clareza
- Claramente especificada
- Facilidade para iniciantes
- 72/100