Skip to content

dstack-ingress/route53: preserve accounturi in Route53 CAA records - #1

Open
Garandor wants to merge 1 commit into
mainfrom
cl4wb0t/test-caa-consistency
Open

dstack-ingress/route53: preserve accounturi in Route53 CAA records#1
Garandor wants to merge 1 commit into
mainfrom
cl4wb0t/test-caa-consistency

Conversation

@Garandor

@Garandor Garandor commented Mar 31, 2026

Copy link
Copy Markdown
Owner

Summary

  • Route53's create_caa_record() was ignoring caa_record.value and hard-coding bare "letsencrypt.org" as the CAA issuer, stripping the accounturi parameter required for strict CAA enforcement.
  • Fixed to use the caller-provided value (matching Cloudflare and Linode behavior), and to replace any existing bare LE entries with the accounturi-restricted version.
  • Added a cross-provider test (test_caa_accounturi.py) that verifies all providers preserve accounturi — fails on the old code, passes on the fix.

Test plan

  • Test fails against old Route53 code (stashed fix, ran test → Route53 FAIL)
  • Test passes against fixed Route53 code (restored fix, ran test → all 3 PASS)
  • After deploy: dig CAA <domain> +short should show accounturi= in the letsencrypt.org entry

🤖 Generated with Claude Code

The Route53 create_caa_record() was ignoring caa_record.value and
hard-coding bare "letsencrypt.org" as the CAA issuer, stripping the
accounturi parameter needed for strict CAA enforcement. Now uses the
caller-provided value (like Cloudflare and Linode do). Also adds a
cross-provider test verifying accounturi is preserved.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Garandor Garandor changed the title fix(ingress): preserve accounturi in Route53 CAA records dstack-ingress/route53: preserve accounturi in Route53 CAA records Mar 31, 2026
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