Update deny-lists for new customDomains is_default property

[pcentgraf]

Checklist

• I have looked into the README and have not found a suitable solution or answer.
• I have looked into the documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have upgraded to the latest version of this tool and the issue still persists.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

The Auth0 Management API has recently been updated to add a new 'is_default' property to customDomains. The deny-lists for create and update should be updated to exclude this property from the payload. Adding this property name to the two lists in the code below should be a sufficient fix.

auth0-deploy-cli/src/tools/auth0/handlers/customDomains.ts

Line 54 in 8527db1

stripCreateFields: [

Expectation

It should be possible to trivially re-submit tenant configuration retrieved from Auth0 back to Auth0 for entities that have not changed.

Reproduction

1. Given an Auth0 tenant with multiple customDomains.
2. When submitting a change to Auth0 using a yaml file previously retrieved and by this CLI...
3. Then Auth0 rejects the payload, because it contains the read-only property 'is_default'.

Deploy CLI version

8.25.0

Node version

22.22.0

[kushalshit27]

Thank you for reporting this issue! Our team has started working on it.