DXCDT-540: Prevent null string literal when importing custom text prompts #821
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 using Terraform config-driven imports with the
auth0_prompt_custom_text
resource, there can be cases where thebody
property gets generated literally as"null"
. This occurred because the Management API returns an empty object string literal"{}"
for unconfigured custom text prompts and would get interpreted somewhere in the Terraform SDK asnil
which would cause a bit of havoc when marshalling back to a string.With this PR, the generated custom text prompt looks like this:
This is preferred because it matches the output of the Management API.
🔬 Testing
Added unit tests to enable empty object as body property. Manually verified that config-driven import works as expected.
📝 Checklist