Create a new S3 component that allows a route to finish by putting a file in an S3 bucket.
It is not required to allow a file / event to be triggered by a S3 file event as it is thought that this kind of flow will be handled within AWS itself. It doesn't seem wise to have a poll against an S3 bucket for a file (but should anyone need it, then this can be done at a later stage).
For now, only the to route is needed in the component.
This will also serve as the foundation for AWS components in terms of auth etc.
All AWS components should rely on DI for setup so that a localstack injection can be done especially with integration testing. However no unit tests should rely on localstack. We should also investigate if there is any value in running the integration tests as part of CI-CD or whether we do PACT testing (pact may leverage better results).
Create a new S3 component that allows a route to finish by putting a file in an S3 bucket.
It is not required to allow a file / event to be triggered by a S3 file event as it is thought that this kind of flow will be handled within AWS itself. It doesn't seem wise to have a poll against an S3 bucket for a file (but should anyone need it, then this can be done at a later stage). For now, only the to route is needed in the component.
This will also serve as the foundation for AWS components in terms of auth etc.
All AWS components should rely on DI for setup so that a localstack injection can be done especially with integration testing. However no unit tests should rely on localstack. We should also investigate if there is any value in running the integration tests as part of CI-CD or whether we do PACT testing (pact may leverage better results).