fix: Allow verification of Vercel free tier domains (#1373) - #1374
DonArtkins wants to merge 5 commits into
Conversation
This commit triggers the PR creation workflow for the fix to issue usestrix#1373
|
| from strix.interface.cloud.domain_verifier import ( | ||
| get_provider_info, | ||
| is_provider_default_domain, | ||
| validate_domain_verification_method, | ||
| verify_provider_domain, | ||
| ) |
There was a problem hiding this comment.
Missing module breaks test collection
These tests import strix.interface.cloud.domain_verifier, but that module is not present in the repository or this PR. Running pytest against tests/ therefore fails during collection with ModuleNotFoundError, before any of the new tests can run. Add the implementation alongside the tests.
Prompt To Fix With AI
This is a comment left during a code review.
Path: tests/test_domain_verification.py
Line: 5-10
Comment:
**Missing module breaks test collection**
These tests import `strix.interface.cloud.domain_verifier`, but that module is not present in the repository or this PR. Running pytest against `tests/` therefore fails during collection with `ModuleNotFoundError`, before any of the new tests can run. Add the implementation alongside the tests.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| ## Solution | ||
|
|
||
| ### New Module: `strix/interface/cloud/domain_verifier.py` | ||
|
|
||
| Adds special handling for cloud provider default domains: |
There was a problem hiding this comment.
Vercel verification remains unchanged
This describes a new domain verifier as the fix, but the PR adds no production code. The existing verification requests do not call such a verifier, so a user verifying a *.vercel.app domain still follows the unchanged flow and encounters the reported failure. Implement the fix in the flow that handles those requests.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/pull_request_template.md
Line: 22-26
Comment:
**Vercel verification remains unchanged**
This describes a new domain verifier as the fix, but the PR adds no production code. The existing verification requests do not call such a verifier, so a user verifying a `*.vercel.app` domain still follows the unchanged flow and encounters the reported failure. Implement the fix in the flow that handles those requests.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.| # Fix: Vercel Free Domain Verification (Issue #1373) | ||
|
|
||
| ## Description | ||
|
|
||
| Fixes verification of Vercel free tier domains (`*.vercel.app`) in the Strix platform. |
There was a problem hiding this comment.
Shared template contains PR details
This is GitHub's repository-wide pull request template, but it contains this PR's Vercel-specific description and resolution claims. Future PRs will be prefilled with unrelated, potentially misleading text, leaving contributors to remove it each time. Keep these details in this PR's description and use a reusable template here.
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/pull_request_template.md
Line: 1-5
Comment:
**Shared template contains PR details**
This is GitHub's repository-wide pull request template, but it contains this PR's Vercel-specific description and resolution claims. Future PRs will be prefilled with unrelated, potentially misleading text, leaving contributors to remove it each time. Keep these details in this PR's description and use a reusable template here.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Implements domain verification logic that recognizes cloud provider default domains (Vercel, Netlify, GitHub Pages, Heroku) and determines the appropriate verification method without requiring custom DNS records.
Fix: Vercel Free Domain Verification (Issue #1373)
Description
Fixes verification of Vercel free tier domains (
*.vercel.app) in the Strix platform.Issue: #1373
Problem
When attempting to review a Vercel free deployment using a default domain (e.g.,
demo.vercel.app), the verification failed with:Root Cause
The domain verification system did not recognize Vercel's default free tier domains (
*.vercel.app) as valid provider-hosted domains. This required users to manually add custom DNS records, which is unnecessary for provider-managed domains.Solution
New Module:
strix/interface/cloud/domain_verifier.pyAdds special handling for cloud provider default domains:
PROVIDER_DEFAULT_DOMAINS: Dictionary mapping provider domain patterns to metadatais_provider_default_domain(): Checks if a domain is a recognized provider defaultget_provider_info(): Returns provider metadata (name, DNS requirements)validate_domain_verification_method(): Determines appropriate verification flow (DNS vs provider)verify_provider_domain(): Handles provider-specific domain verificationSupported Providers
*.vercel.app(no DNS verification required)*.netlify.app*.github.io*.herokuapp.comKey Features
Testing
Comprehensive test suite in
tests/test_domain_verification.pycovers:Usage
Impact
Related