Skip to content

fix: filter esms in sqs poller#447

Merged
hectorvent merged 1 commit intofloci-io:mainfrom
bkindersleytrulioo:fix/sqs-poller
Apr 15, 2026
Merged

fix: filter esms in sqs poller#447
hectorvent merged 1 commit intofloci-io:mainfrom
bkindersleytrulioo:fix/sqs-poller

Conversation

@bkindersleytrulioo
Copy link
Copy Markdown
Contributor

Summary

Closes #446

Type of change

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

AWS Compatibility

SqsEventSourcePoller should only start polling for event source mappings that have sqs as a source. This matches what the other pollers are doing

Checklist

  • ./mvnw test passes locally (well, the same tests fail on main, anyways)
  • New or updated integration test added.
    (i'm not really sure how to test this?)
  • Commit messages follow Conventional Commits

@bkindersleytrulioo
Copy link
Copy Markdown
Contributor Author

the failed compatibility tests don't seem particularly related to what i changed?
(they are related to SES and ECR?)

@bkindersleytrulioo bkindersleytrulioo changed the title (fix) filter esms in sqs poller fix: filter esms in sqs poller Apr 14, 2026
@hectorvent
Copy link
Copy Markdown
Collaborator

Hi @bkindersleytrulioo,

Thank you for the PR. I reran the test to double check the result, it could be some race conditions between services created by floci.

@hectorvent
Copy link
Copy Markdown
Collaborator

Oh, tests finished all green.

@hectorvent hectorvent merged commit bf67c61 into floci-io:main Apr 15, 2026
17 of 19 checks passed
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.

[BUG] SqsEventSourcePoller init doesn't filter for sqs source

2 participants