Skip to content

(only CI)#2

Open
steve-hb wants to merge 1 commit into
mainfrom
fix/concurrency-limit-warning
Open

(only CI)#2
steve-hb wants to merge 1 commit into
mainfrom
fix/concurrency-limit-warning

Conversation

@steve-hb
Copy link
Copy Markdown

When PutFunctionConcurrency hits the regional reservation cap, the LimitExceededException response is AWS-correct but the cause is invisible in floci logs. Operators see only terraform retrying for minutes (AWS SDK Go v2 plus the provider's MaxAttempts=25) while the underlying reason (total reservations exceed regionLimit minus unreservedMin) sits silently in the limiter.

Emit a WARN on every limit hit with the offending numbers and the env var to raise the cap. Error code, body and status remain identical to real AWS; this is observability only.

Summary

Type of change

  • Bug fix (fix:)
  • New feature (feat:)
  • Breaking change (feat!: or fix!:)
  • Docs / chore

AWS Compatibility

Checklist

  • ./mvnw test passes locally
  • New or updated integration test added
  • Commit messages follow Conventional Commits

When PutFunctionConcurrency hits the regional reservation cap, the
LimitExceededException response is AWS-correct but the cause is
invisible in floci logs. Operators see only terraform retrying for
minutes (AWS SDK Go v2 plus the provider's MaxAttempts=25) while the
underlying reason (total reservations exceed regionLimit minus
unreservedMin) sits silently in the limiter.

Emit a WARN on every limit hit with the offending numbers and the
env var to raise the cap. Error code, body and status remain
identical to real AWS; this is observability only.
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.

1 participant