Skip to content

fix: clean up Route53 provider, remove wildcard domain support#2

Closed
cl4wb0t wants to merge 1 commit intomainfrom
feat/route53-cleanup
Closed

fix: clean up Route53 provider, remove wildcard domain support#2
cl4wb0t wants to merge 1 commit intomainfrom
feat/route53-cleanup

Conversation

@cl4wb0t
Copy link
Copy Markdown
Owner

@cl4wb0t cl4wb0t commented Mar 23, 2026

Summary

  • Trim verbose docstrings in route53.py
  • Fix typos in Route53 notes in DNS_PROVIDERS.md
  • Add missing volumes: block to Route53 compose example
  • Add route53 to DNS_PROVIDER choices list
  • Remove wildcard domain handling (cert_dir_name, wildcard TXT prefix, wildcard CAA issuewild tag) — use DOMAIN directly for cert paths
  • Remove "Wildcard Domain Support" section from README

Files Changed

File Change
scripts/dns_providers/route53.py Trim docstrings
scripts/entrypoint.sh Remove wildcard handling, use ${DOMAIN} for cert paths
scripts/functions.sh Remove cert_dir_name()
scripts/generate-evidences.sh Use ${domain} directly
DNS_PROVIDERS.md Add route53 to choices, fix typos, add missing volumes
README.md Remove Wildcard Domain Support section

Test plan

  • Verify Route53 provider still works for standard (non-wildcard) domains
  • Verify cert paths resolve correctly with ${DOMAIN}
  • Verify other providers (Cloudflare, Linode) unaffected

Cherry-picked from Dstack-TEE/dstack-examples#83
Tracks: CPL-139

🤖 Generated with Claude Code

- Trim verbose docstrings in route53.py
- Fix typos in DNS_PROVIDERS.md Route53 notes
- Add missing volumes block to Route53 compose example
- Add route53 to DNS_PROVIDER choices list
- Remove wildcard domain handling (cert_dir_name, wildcard TXT prefix,
  wildcard CAA issuewild tag) from entrypoint.sh and functions.sh
- Remove Wildcard Domain Support section from README
- Use DOMAIN directly for cert paths instead of cert_dir_name

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@cl4wb0t
Copy link
Copy Markdown
Owner Author

cl4wb0t commented Mar 23, 2026

No longer needed

@cl4wb0t cl4wb0t closed this Mar 23, 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