Skip to content

Conversation

@szuecs
Copy link
Member

@szuecs szuecs commented Jun 22, 2025

feature: letsencrypt http.Handler integration via autocert with different storage/cache systems to be used by different deployments

@szuecs szuecs added enhancement minor no risk changes, for example new filters do-not-merge labels Jun 22, 2025
@szuecs szuecs force-pushed the feature/letsencrypt branch from efbe6d7 to e6b4ba5 Compare August 26, 2025 19:09
…rent storage/cache systems to be used by different deployments

Signed-off-by: Sandor Szuecs <[email protected]>
@szuecs szuecs force-pushed the feature/letsencrypt branch from e6b4ba5 to 9aa7e75 Compare November 13, 2025 22:05
@zalando-robot
Copy link

Deployment Checklist

This change falls under the deployment policy.

💁 Since Nov 10th, we are in the RED deployment zone. This means all changes released to production must adhere to the following requirements:

  • Detailed release notes are provided in this PR’s description.
  • Thorough load-testing has been performed, and is documented in the description/comment.
  • You can enable/disable the change via feature toggles, and have confirmed these toggles work as expected.
  • Technical review: A Principal Engineer, Engineering Manager or Head of Engineering have green-lit your changes, and the reviewer is named in the description/comments.
  • Application Owner (Director+) approval is given about the PR, and the approver is named in the description/comments.

👉 Regardless of which boxes you click in this comment, merge/deployment will not be blocked.
Reports about deployment policy adherence will be circulated daily.

@szuecs szuecs marked this pull request as draft November 13, 2025 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge enhancement minor no risk changes, for example new filters

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants