Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

better support for Forms, specifically modifications #1076

Open
1 task done
jdavisclark opened this issue Nov 13, 2024 · 0 comments
Open
1 task done

better support for Forms, specifically modifications #1076

jdavisclark opened this issue Nov 13, 2024 · 0 comments
Labels
🌱 feature New feature or request

Comments

@jdavisclark
Copy link

jdavisclark commented Nov 13, 2024

Checklist

Describe the problem you'd like to have solved

I know the Forms product is really new, so im mostly just happy that there's any support in this provider, but the auth0_form resource type is really difficult to work with. If you simply create an auth0_form with lots of steps/nodes, run an apply to create it, and then make a change + apply again terraform will detect the change and the update API call will fail. It can not handle modifications in any scenario I have tried.

Describe the ideal solution

Ideally I think I'd like to see the auth0_form resource type broken up in to a parent form, and then lots of individual resources for each step/node (basically anything with an ID becomes it's own terraform resource??). Also, real typed properties with documentation for everything; the encoded json blob is a pain to work with.

But, obviously the underlying request here is "I need to be able to make changes to an existing form without jumping through tons of hoops and recreating it every single time". It has to be possible because the forms UI can do it, but the auth0_form provider can not.

Alternatives and current workarounds

At first I set it up so the Form nodes and css were defined in local variables, and the form resource itself had replacement policies defined based on those MD5s changing. This kind of worked, but at some point phantom "changes" that get detected between runs started happening that still somehow trigger modification rather than replacements (which will fail).

e.g. Even with that hash replacement lifecycle in place: I can run a terraform apply to create a new form, and then run it again with no changes anywhere, and it will detect a deletion of the multiline: false config property of TEXT inputs regardless of what is or isn't defined in the template and attempt to modify the resource rather than replace it (which fails, since almost all modifications to an auth0_form fail).

Right now, my only workaround is to completely replace the form every single time terraform runs, via a lifecycle replacement policy tied to the current timestamp.

Additional context

No response

@jdavisclark jdavisclark added the 🌱 feature New feature or request label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌱 feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant