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

fix #2151 | add retry on HTTP 423 to okta_group_rule #2258

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

exitcode0
Copy link
Contributor

@exitcode0 exitcode0 commented Mar 28, 2025

fixes #2151


I've reached out to Okta support about this behavior in Support Cases `02157630` and `02192142`

I was told that there are no plans to change the HTTP 423 response code
The HTTP 423 response code is sometimes returned by the Okta API when modifying multiple group rules in rapid succession.
The current behavior when the provider gets a HTTP 423 is to bail out from the entire terraform apply
This is an over reaction (imo) as the request will often succeed if immediately retried


I'm open to suggestions and/or guidance about how to implement this change, especially if there is a better approach I should take instead

I added the logic to the okta_group_rule resource as I wanted to limit the change in behavior/functionality to only this resource, which rules out making the change to the SDK request executor(s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Policy lock exception, HTTP Status: 423 Locked
1 participant