Skip to content

Add acme-az-aca to clients.json - #2383

Open
emilgruzalski wants to merge 1 commit into
letsencrypt:mainfrom
emilgruzalski:add-acme-az-aca
Open

emilgruzalski wants to merge 1 commit into
letsencrypt:mainfrom
emilgruzalski:add-acme-az-aca

Conversation

@emilgruzalski

Copy link
Copy Markdown

acme-az-aca is an ACMEv2 client written in Go (built on lego) for Azure Container Apps. It runs as a long-lived sidecar: it answers HTTP-01 challenges routed to it by the Container Apps ingress, converts the issued certificate to PFX in memory and imports it into Azure Key Vault, where Container Apps picks it up for custom domain bindings. It persists its ACME account key in Key Vault, so restarts reuse the same account instead of registering new ones. It is Apache-2.0 licensed and ships as signed multi-arch images, and an end-to-end test runs it against Pebble.

This PR appends it to the end of the list under Microsoft Azure and updates lastmod.

Listing criteria:

  • Trademark policy: the project name does not use "Let's Encrypt", the README mentions Let's Encrypt only to describe what the tool does, and no logos are used.
  • Not browser-based, automatic renewals: it runs unattended in the container, checks the certificate every 24h and renews 30 days before expiry (both configurable).
  • Randomized renewal times: checks are scheduled from container start, not at a fixed wall-clock time, and feat: randomize renewal waits by ±10%; bump go-jose to v4.1.7; changelog for 1.3.1 emilgruzalski/acme-az-aca#35 randomizes each wait by ±10% so instances deployed together drift apart.
  • End of the relevant section: appended as the last entry of list.
  • lastmod: set to 2026-11-04.

🤖 Generated with Claude Code

acme-az-aca is a Go ACMEv2 client that runs as a sidecar in Azure
Container Apps, answers HTTP-01 challenges and imports renewed
certificates into Azure Key Vault. Appended to the end of the list
under "Microsoft Azure"; lastmod updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant