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

Auth0 Actions API renamed the non beta Node18 runtime #705

Closed
6 tasks done
jmymy opened this issue Jul 11, 2023 · 4 comments
Closed
6 tasks done

Auth0 Actions API renamed the non beta Node18 runtime #705

jmymy opened this issue Jul 11, 2023 · 4 comments
Labels
🪲 bug Something isn't working

Comments

@jmymy
Copy link

jmymy commented Jul 11, 2023

Checklist

  • I have looked into the README and have not found a suitable solution or answer.
  • I have looked into the documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have upgraded to the latest version of this provider and the issue still persists.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

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 not node18 as that is from the Beta runtime of it.

You can see the drift in the terraform plan

runtime :
"node18-actions"
change to
"node18"

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

  • Add an action in TF with runtime node16.
  • Open the Auth0 UI and edit and click upgrade to recommended runtime
  • Look at the drift and see the runtime returned by api is node18-actions.
    Screenshot 2023-07-11 at 11 08 14 AM
  • If you change to node18 in TF, the UI shows that it is the beta version of node 18
    Screenshot 2023-07-11 at 11 08 31 AM

Auth0 Terraform Provider version

0.50.0

Terraform version

1.5.2

@jmymy jmymy added the 🪲 bug Something isn't working label Jul 11, 2023
@willvedd
Copy link
Contributor

@jmymy Thanks for opening this issue. I can confirm that now that node 18 is GA, it is using the node18-actions designation, while node18 is designated for beta. You can expect us to update this validation very soon.

@sergiught
Copy link
Contributor

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.

terraform {
  required_providers {
    auth0 = {
      source  = "auth0/auth0"
      version = "1.0.0-beta.0"
    }
  }
}

📚 Resources

Quickstart | Documentation | Migration Guide | Changelog

@jmymy
Copy link
Author

jmymy commented Jul 20, 2023

@sergiught

Terraform v1.5.3
on darwin_arm64
+ provider registry.terraform.io/auth0/auth0 v1.0.0-beta.0
╷
│ Error: expected runtime to be one of [node12 node16 node18], got node18-actions
│
│   with auth0_action.org_redirect,
│   on auth0-tenant.tf line 93, in resource "auth0_action" "org_redirect":
│   93:   runtime  = "node18-actions"
│
╵

@sergiught
Copy link
Contributor

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 node18 and the GA version as node18-actions and as well that the node18 beta will not be available any more after september. So the current value of node18 is behind the scenes what the API will perceive as node18-actions.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants