What happened?
Terraform resources such as https://registry.terraform.io/providers/auth0/auth0/latest/docs/resources/prompt_custom_text show a string escaping syntax like $${expression}, because Auth0 uses the same
escaping syntax internally, as Terraform does.
This is correct when using upjet in TF cli invocation mode, as those inline strings pass through the terraform cli. But once you switch to tfpluginsdk mode, the Terraform string interpolation handling is no longer in play, and the double doller is no longer correct.
When using any direct-code-invocation mode, those examples would have to read ${expression}.
Edgiest edge case, i know.
What happened?
Terraform resources such as https://registry.terraform.io/providers/auth0/auth0/latest/docs/resources/prompt_custom_text show a string escaping syntax like
$${expression}, because Auth0 uses the sameescaping syntax internally, as Terraform does.
This is correct when using upjet in TF cli invocation mode, as those inline strings pass through the terraform cli. But once you switch to tfpluginsdk mode, the Terraform string interpolation handling is no longer in play, and the double doller is no longer correct.
When using any direct-code-invocation mode, those examples would have to read
${expression}.Edgiest edge case, i know.