fix #2151 | add retry on HTTP 423 to okta_group_rule #2258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 codeThe 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 entireterraform 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)