Conversation
|
@exekias @kaiyan-sheng I commented out the integration tests for now. The setup of these tests looks rather 'complicated' and I wonder if we can simplify them a little. I didn't spend much time learning about the purpose of each test. Some help would be appreciated (Note: no need for hurry, I didn't plan to have it ready for 7.9). |
💔 Build FailedExpand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
@urso Thank you so much for converting |
|
Closing. Work is continued in #20005 |
What does this PR do?
Move s3 input to input v2 API.
This change splits the internal s3Input into s3Input and s3Collector. The s3Input is responsible for configuration only.
The unit tests have been modified, but the integration tests need some more work.
Why is it important?
Update to v2 input API.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Manual testing:
s3:ObjectCreated:*type to your Amazon SQS queue.For running the
s3_integration_test.go, environment variables are needed. For example:Related issues