DXCDT-348: Manage ul body in branding resource only if custom domains are set #446
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.
🔧 Changes
When no custom domains are set and we are trying to manage the universal login body template we get an error from the api:
Error: 400 Bad Request: This feature requires at least one custom domain to be configured for the tenant.
.The current logic only checks if a tenant flag is set to true, but that's unfortunately flawed.
In this PR we replace that tenant flag check with checking for available custom domains before managing the universal login template body.
📚 References
🔬 Testing
📝 Checklist