🤖 triggering CI on branch 'release-next' after synching from upstream/main#104
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: serverless-qe The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: serverless-qe The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
…lated services (#104) * aws-s3-sink - allow testing against real AWS services * aws-eventbridge-sink - programatically get arn of new queue * aws-eventbridge-sink - decouple test code from infrastructure setup * aws-eventbridge-sink - add AWS variant of test * aws-sqs-sink - decouple test code from infrastructure setup * aws-sqs-sink - add AWS variant of test * aws-sns-sink - decouple test code from infrastructure setup * aws-sns-sink - add AWS variant of test * aws-sqs-source - decouple test code from infrastructure setup * aws-sqs-source - add AWS variant of test * aws-s3-source - decouple test code from infrastructure setup * aws-s3-source - add AWS variant of test * aws-ddb-streams-source - decouple test code from infrastructure setup * aws-ddb-streams-source - add AWS variant of test * add AWS cleanup script * switch to global maven profile instead of module's specific profiles * update README
1 participant
No description provided.