Skip to content

Conversation

@tbroden84
Copy link
Contributor

WHY are these changes introduced?

API backend will later start to respond with status 423 (locked) if server not configured.

Reference: #436

WHAT is this pull request doing?

  • Updates generic retry to handle status 423 with retry requests.
  • Updates older retries to handle status 423 and 503 with retry requests.
    Will later use generic retry, once they are migrated.

HOW was this pull request be tested?

Current VCR-test fixtures, no real attempt made.

@tbroden84 tbroden84 requested a review from a team as a code owner December 5, 2025 15:51
Comment on lines +82 to +84
case 423:
tflog.Debug(ctx, fmt.Sprintf("resource %s is locked, will try again, attempt=%d", request.resourceName, request.attempt))
// Intentionally fall through to retry logic below
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If would be great to log a warning like we do for 400, with the message from the response:

} else if msg, ok := (*request.failed)["message"].(string); ok {

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.

3 participants