-
Notifications
You must be signed in to change notification settings - Fork 163
[Don't merge] feat: Support for Multiple Custom Domains #1113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1113 +/- ##
==========================================
+ Coverage 80.11% 80.14% +0.02%
==========================================
Files 131 131
Lines 4878 4875 -3
Branches 959 958 -1
==========================================
- Hits 3908 3907 -1
+ Misses 562 561 -1
+ Partials 408 407 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
- Standardize TypeScript ignore comments with proper spacing - Standardize inline comment formatting with consistent spacing - Add comprehensive test coverage for custom domain update functionality
customDomains: | ||
- domain: my_domain.com | ||
type: auth0_managed_certs | ||
domain_metadata: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we include tls_policy too..?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure
stripCreateFields: ['status', 'primary', 'verification'], | ||
stripUpdateFields: [ | ||
'status', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also see another field name certificate
(read-only field similar to verification) in tf-provider PR, Any reason on not including in deploy-cli..?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, this was not added in the previous implementation, but we can add it now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I saw it being added in the stripUpdateFields
, but not in the schema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, because the schema is used for input validation, certificate
does not need validation.
status: 'ready', // should be stripped | ||
primary: true, // should be stripped | ||
verification: { method: 'cname' }, // should be stripped | ||
verification_method: 'cname', // should be stripped |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we have verification_method
field separately in domain.. As we already have a field method
in verifications!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
verification
and verification_method
can co-exist in the configuration at the same time. This function tests that they are stripped properly, as per our logic during update.
…auth0-deploy-cli into DXCDT-1075-mcd-ea-support
TODO: update node-sdk
🔧 Changes
Example:
📌 Note:
primary
field is deprecated and may be removed in future versions.verification_method
field is deprecated and may be removed in future versions.📚 References
🔬 Testing
TDB
📝 Checklist