-
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
Setting default idle_session_lifetime
on tenant import
#849
Setting default idle_session_lifetime
on tenant import
#849
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #849 +/- ##
==========================================
+ Coverage 89.89% 89.92% +0.02%
==========================================
Files 101 101
Lines 13785 13793 +8
==========================================
+ Hits 12392 12403 +11
+ Misses 989 987 -2
+ Partials 404 403 -1
|
Thank you for the fix, I just ran into this issue with If I'm importing an existing tenant that has been functioning fine for our application, but I'm weary about changing these values. |
@dangbert both session lifetime values are required to be positive, non-zero values. The zeros you're seeing are the Go defaults being used in absence of the explicit values being returned from the tenant. In the Auth0 Management API, if the session lifetime values haven't been adjusted, they'll inherit the defaults and not be explicitly defined in your specific tenant object. The tenant that you're exporting to will behave the same as the existing tenant. Though I recommend to review the session lifetime values with your team to make sure they work for your particular business case. |
Thanks for the clarification @willvedd. That is indeed consistent with a later discussion I had with my team, so I've omitted the values as you suggested. Thanks for your fix and guidance, the timing was perfect 👍 |
🔧 Changes
Sometimes when importing a
auth0_tenant
resource, theidle_session_lifetime
field gets set to zero. Normally this isn't such a problem because subsequent plans or applies will have this value set to the default value of 72. However, the Auth0 CLI'sauth0 tf generate
command will get hung up on the zero value because it violates the schema's validation. This default is necessary because not all tenants will have theidle_session_lifetime
value set, particularly if it is a new tenant.📚 References
🔬 Testing
Manual verification on a new tenant. Difficult to add to acceptance tests because our testing tenants will always have this value set; it is important to have it not set for testing.
📝 Checklist