feat(domains): Simplify regions and automate domain HTTPS - #190
Merged
Merged
Conversation
Replace regional certificate and DNS-provider management with manual CNAME entries, persistent DNS checks, and platform-managed customer certificates. Refs #189
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Regional CNAME targets no longer require DNS-provider credentials or their own certificates. Administrators configure entry DNS manually; verified customer domains receive their own HTTPS certificates.
hk_1andhk_frick; allow one entry per existing region.Validation
just qualitypassed: formatting, Clippy with warnings denied, workspace tests/check/build, Console checks/tests/build, and license checks. Control API: 488 tests passed; Console: 235 tests passed.git diff --checkpassed.Tracking
Closes #189.
Parent capability: #179. Related work: #181.
Known Limitations
vp exec tsc --noEmitcheck remains blocked by existing repository type issues, including missing React/Node type declarations. The repository's required Console checks, tests, and production build pass.