-
Notifications
You must be signed in to change notification settings - Fork 89
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
Auth0 Actions API renamed the non beta Node18 runtime #705
Comments
@jmymy Thanks for opening this issue. I can confirm that now that node 18 is GA, it is using the |
Hey @jmymy 👋🏻 This got fixed now as part of the v1.0.0-beta.0 release! 🙌🏻 Please give it a try and let us know if you encounter any issues.
📚 Resources |
|
Hey @jmymy 👋🏻 Thanks for following back on this. In order to improve the developer experience, we decided to not offer the beta version of node18 as a valid option considering that the API names it as This is mentioned in our migration guide over here: https://github.com/auth0/terraform-provider-auth0/blob/main/MIGRATION_GUIDE.md#actions-node-18-runtime-beta. So in summary, choosing now node18 will opt you into the GA version of node18 (what the API understands as node18-actions). Let me know if you have any questions. |
Checklist
Description
It appears that the auth0 API has a different value for node18 runtime from when it was in beta to now GA.
When editing in the UI, and selecting the new runtime of node18, the actual backend runtime is
node18-actions
and notnode18
as that is from the Beta runtime of it.You can see the drift in the terraform plan
Expectation
Be able to change to use the runtime of
runtime: "node18-actions"
but field validation will not allow it on the TF side.Reproduction
node16
.node18-actions
.node18
in TF, the UI shows that it is the beta version of node 18Auth0 Terraform Provider version
0.50.0
Terraform version
1.5.2
The text was updated successfully, but these errors were encountered: