Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 Processor #173

Open
jem-davies opened this issue Nov 23, 2024 · 0 comments
Open

S3 Processor #173

jem-davies opened this issue Nov 23, 2024 · 0 comments
Labels
good first issue Good for newcomers

Comments

@jem-davies
Copy link
Collaborator

jem-davies commented Nov 23, 2024

Consider adding an "S3 Processor" that would function similar to the http processor, where we could replace the message contents with the s3 object data.

This would be of benefit when using the streaming-objects-on-upload-with-sqs pattern, but you would like to also have access to the SQS message data, or in the case of the 'sqs extended library for large messages' you would like to access s3 on some condition of the SQS message data.

So you would be able to do something like:

input:
  aws_sqs:
    url: foo

pipeline:
  processors:
    - branch:
      result_map: |
          root.key = this.sqs.key
          
      processors: 
        - aws_s3:
          bucket: foo_bucket
          key: ${! this.key }

      result_map: |
        root.s3_data = this
@jem-davies jem-davies added the good first issue Good for newcomers label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant