Skip to content

fix: remove http yaml#3097

Open
Viczei wants to merge 2 commits intomasterfrom
fix/remove-http-yaml
Open

fix: remove http yaml#3097
Viczei wants to merge 2 commits intomasterfrom
fix/remove-http-yaml

Conversation

@Viczei
Copy link
Copy Markdown
Contributor

@Viczei Viczei commented Mar 26, 2026

No description provided.

@Viczei Viczei self-assigned this Mar 26, 2026
@Viczei Viczei requested review from a team as code owners March 26, 2026 16:47
@revu-bot revu-bot bot requested a review from revu-bot March 26, 2026 16:47
Copy link
Copy Markdown
Collaborator

@revu-bot revu-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ PR Review Skipped

3 validation issues found. Review thresholds can be adjusted in .revu.yml.

See why it was skipped and detailed metrics

Issues Found

1. This PR changes 186 files, which exceeds the limit of 25 files.

Suggestion: Consider breaking this PR into smaller, more focused changes. Large PRs are harder to review effectively and may contain unrelated changes.

2. This PR has 52442 lines of diff, which exceeds the limit of 15000 lines.

Suggestion: Consider splitting this PR into smaller chunks. Large diffs are difficult to review thoroughly and may hide important issues.

3. This PR contains files that exceed the size limit: '.kontinuous/charts/redis/values.schema.json' (3299 lines of changes), 'pnpm-lock.yaml' (12609 lines of changes), 'yarn.lock' (15749 lines of changes), which exceeds the limit of 3000. The limit is 3000 lines per file.

Suggestion: Consider refactoring large changes into smaller, more focused modifications. Large file changes are harder to review and understand.

PR Metrics

  • Total files changed: 186
  • Reviewable files: 186
  • Diff size: 52442 lines
  • Documentation files: 5
  • Largest file change: 15749 lines
  • Addition/Deletion ratio: 1.59

This validation helps ensure the bot focuses on PRs where automated review provides the most value.

@Viczei Viczei changed the base branch from alpha to master March 26, 2026 16:47
Traefik CRDs (IngressRoutes, Middlewares) are managed manually on the
cluster and the CI service account lacks RBAC permissions to apply them,
causing every production deployment to fail.

Move http.yaml to archive/ so it is no longer applied by Kontinuous
while keeping it as reference.
@Viczei Viczei requested a review from revu-bot March 26, 2026 16:47
Copy link
Copy Markdown
Collaborator

@revu-bot revu-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary: Move http.yaml to Archive

This PR renames .kontinuous/env/prod/templates/http.yaml to .kontinuous/env/prod/archive/http.yaml — effectively removing it from the active Kubernetes deployment pipeline by moving it out of the templates/ directory.

Key Observations

  • No code changes — the file content is identical; only the path changed.
  • Deployment impact — moving the file out of templates/ means all the Kubernetes resources defined in it (Certificates, IngressRoutes, Middlewares) will no longer be applied by kontinuous on the next deployment.
  • No cleanup of live resources — the existing resources in the cluster are not explicitly deleted by this PR.

Issues Found

File Severity Issue
.kontinuous/env/prod/archive/http.yaml IMPORTANT Archiving without deleting live cluster resources risks orphaned resources
.kontinuous/env/prod/archive/http.yaml MINOR No README or comment explaining why the file was archived

@Viczei Viczei temporarily deployed to build-review-auto March 26, 2026 16:49 — with GitHub Actions Inactive
@Viczei Viczei temporarily deployed to build-review-auto March 26, 2026 16:49 — with GitHub Actions Inactive
@Viczei Viczei temporarily deployed to build-review-auto March 26, 2026 16:49 — with GitHub Actions Inactive
@Viczei Viczei temporarily deployed to build-review-auto March 26, 2026 16:49 — with GitHub Actions Inactive
@tokenbureau
Copy link
Copy Markdown

tokenbureau bot commented Mar 26, 2026

🎉 Deployment for commit fbabf4c :

Ingresses
Docker images
  • 📦 docker pull busybox:1.36
  • 📦 docker pull harbor.fabrique.social.gouv.fr/egapro/egapro/api:preprod-fbabf4ccd898898ad409bef5f7f19b86b2ab272d
  • 📦 docker pull harbor.fabrique.social.gouv.fr/egapro/egapro/app:preprod-fbabf4ccd898898ad409bef5f7f19b86b2ab272d
  • 📦 docker pull harbor.fabrique.social.gouv.fr/egapro/egapro/files:preprod-fbabf4ccd898898ad409bef5f7f19b86b2ab272d
  • 📦 docker pull harbor.fabrique.social.gouv.fr/egapro/egapro/nginx:preprod-fbabf4ccd898898ad409bef5f7f19b86b2ab272d
  • 📦 docker pull maildev/maildev:2.1.0
  • 📦 docker pull quay.io/keycloak/keycloak:26.0
  • 📦 docker pull sosedoff/pgweb:0.14.1
Debug

Copy link
Copy Markdown
Member

@maxgfr maxgfr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pourquoi on doit faire ça ?

@Viczei
Copy link
Copy Markdown
Contributor Author

Viczei commented Mar 31, 2026

Pourquoi on doit faire ça ?

Parce que ca ne fonctionne pas (ca fait actuellement planter la pipeline de prod) et le http-yaml doit être apply à la main en production.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants