You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the auth0_action resource with a secrets block, Terraform state shows the secret is configured correctly, but the actual secret value in Auth0 remains empty.
After running terraform apply, the secret CAPTURE_PROFILE_DETAILS_FORM_ID should have the value ap_xxxxxxxxxxxx in the Auth0 UI.
Actual Behavior
Terraform state shows the secret with the correct value
terraform plan shows no changes needed
But in the Auth0 UI, the secret value field is empty
Steps to Reproduce
Run terraform apply
Check the Auth0 UI - secret key exists but value is empty
Run terraform plan - shows no changes needed (state drift)
Environment
Terraform version: v1.14.3
Auth0 provider version: ~> 1.36.0
The action is bound to a trigger via auth0_trigger_actions resource
Attempted Solutions
terraform apply -replace terraform apply -replace="auth0_action.post_login_core_action" -replace="auth0_trigger_actions.post_login" Completed successfully but secret value still empty in Auth0 UI
Is this a known bug with the secrets block in auth0_action? Does the provider actually send secret values to the Auth0 API during resource creation?
Thank you for maintaining this provider, and we would be very grateful if you could help us resolve this issue!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When using the
auth0_actionresource with asecretsblock, Terraform state shows the secret is configured correctly, but the actual secret value in Auth0 remains empty.Terraform Configuration
Expected Behavior
After running terraform apply, the secret CAPTURE_PROFILE_DETAILS_FORM_ID should have the value ap_xxxxxxxxxxxx in the Auth0 UI.
Actual Behavior
Steps to Reproduce
Environment
Attempted Solutions
Is this a known bug with the secrets block in auth0_action? Does the provider actually send secret values to the Auth0 API during resource creation?
Thank you for maintaining this provider, and we would be very grateful if you could help us resolve this issue!
Beta Was this translation helpful? Give feedback.
All reactions