Skip to content

[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

Open
wants to merge 11 commits into
base: master
Choose a base branch
from

Conversation

kushalshit27
Copy link
Contributor

@kushalshit27 kushalshit27 commented Jun 16, 2025

TODO: update node-sdk

🔧 Changes

Example:

customDomains:
  - domain: my_domain.com
    .....................
+    domain_metadata:
+      myKey: value

📌 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

  • All new/changed/fixed functionality is covered by tests (or N/A)
  • I have added documentation for all new/changed functionality (or N/A)

@codecov-commenter
Copy link

codecov-commenter commented Jun 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.14%. Comparing base (6c58ffe) to head (1e33910).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@kushalshit27 kushalshit27 marked this pull request as ready for review June 16, 2025 12:39
@kushalshit27 kushalshit27 requested a review from a team as a code owner June 16, 2025 12:39
@kushalshit27 kushalshit27 changed the title Support for Multiple Custom Domains feat: Support for Multiple Custom Domains Jun 16, 2025
@kushalshit27 kushalshit27 marked this pull request as draft June 16, 2025 12:49
- Standardize TypeScript ignore comments with proper spacing
- Standardize inline comment formatting with consistent spacing
- Add comprehensive test coverage for custom domain update functionality
@kushalshit27 kushalshit27 marked this pull request as ready for review June 16, 2025 13:26
@kushalshit27 kushalshit27 changed the title feat: Support for Multiple Custom Domains [ Don't merge] feat: Support for Multiple Custom Domains Jun 16, 2025
@kushalshit27 kushalshit27 changed the title [ Don't merge] feat: Support for Multiple Custom Domains [Don't merge] feat: Support for Multiple Custom Domains Jun 16, 2025
@kushalshit27 kushalshit27 requested a review from ramya18101 June 16, 2025 13:29
customDomains:
- domain: my_domain.com
type: auth0_managed_certs
domain_metadata:
Copy link
Contributor

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..?

Copy link
Contributor Author

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',
Copy link
Contributor

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..?

Copy link
Contributor Author

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.

Copy link
Contributor

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

Copy link
Contributor Author

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
Copy link
Contributor

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!

Copy link
Contributor Author

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.

@kushalshit27 kushalshit27 requested a review from ramya18101 June 18, 2025 06:11
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.

3 participants