Emphasize domain-match in TF generate guide #850
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
Widcket
approved these changes
Sep 26, 2023
willvedd
deleted the
ESD-31286-tf-generate-guide-emphasize-domain-match
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
One piece of feedback received on auto-generating TF configuration is that it isn't well defined that the Auth0 domains for the TF provider and Auth0 CLI need to match. This relationship was supposed to be implied but now made more explicit through this PR.
This accompanies a PR in the Auth0 CLI that enforces the domain match through code.
📚 References
📝 Checklist