aws-cloudtrail: fix acceptance tests

[yaroslav-dudar]

What

Fixed acceptance tests in aws-cloudtrail #5151

How

Describe the solution

Recommended reading order

1. x.java
2. y.python

Pre-merge Checklist

Expand the checklist which is relevant for this PR.

Connector checklist

• Issue acceptance criteria met
• PR name follows PR naming conventions
• Secrets are annotated with airbyte_secret in the connector's spec
• Credentials added to Github CI if needed and not already present. instructions for injecting secrets into CI.
• Unit & integration tests added as appropriate (and are passing)
  • Community members: please provide proof of this succeeding locally e.g: screenshot or copy-paste acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
• /test connector=connectors/<name> command as documented here is passing.
  • Community members can skip this, Airbyters will run this for you.
• Code reviews completed
• Documentation updated
  • README.md
  • docs/SUMMARY.md if it's a new connector
  • Created or updated reference docs in docs/integrations/<source or destination>/<name>.
  • Changelog in the appropriate page in docs/integrations/.... See changelog example
  • docs/integrations/README.md contains a reference to the new connector
  • Build status added to build page
• Build is successful
• Connector version bumped like described here
• New Connector version released on Dockerhub by running the /publish command described here
• No major blockers
• PR merged into master branch
• Follow up tickets have been created
• Associated tickets have been closed & stakeholders notified

Connector Generator checklist

• Issue acceptance criteria met
• PR name follows PR naming conventions
• If adding a new generator, add it to the list of scaffold modules being tested
• The generator test modules (all connectors with -scaffold in their name) have been updated with the latest scaffold by running ./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates then checking in your changes
• Documentation which references the generator is updated as needed.

[yaroslav-dudar]

/test connector=connectors/source-aws-cloudtrail

🕑 connectors/source-aws-cloudtrail https://github.com/airbytehq/airbyte/actions/runs/1093652265
✅ connectors/source-aws-cloudtrail https://github.com/airbytehq/airbyte/actions/runs/1093652265

[sherifnada]

what are the additional fields? should we add them to the schema?

[yaroslav-dudar]

I have optional config to limit amount of records to read. this allows to speedup test execution

more details here - #4122 (comment)

[midavadim]

We should bump the connector version and update files with seeds as well.

[yaroslav-dudar]

/publish connector=connectors/source-aws-cloudtrail

🕑 connectors/source-aws-cloudtrail https://github.com/airbytehq/airbyte/actions/runs/1097445149
✅ connectors/source-aws-cloudtrail https://github.com/airbytehq/airbyte/actions/runs/1097445149