You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use the AWSS3 target with a generic S3 service, such as minio.
Would you please consider adding alternative endpoint configuration parameters, other than ARN?
Benthos for example, works with AWS and generic S3 services because it supports being able to independently specify:
region
endpoint
credentials.id
credentials.secret
credentials.token (optional)
(various other params)
Benthos also uses aws.session, but it creates the session with explicit parameters here
Whereas I think triggermesh creates an unconfigured session here
I'm not a go person, so this is just a guess.
Would you please consider allowing optional additional parameters that can be passed use when the session object is created, so that the s3 target can be used by other s3 providers?
The text was updated successfully, but these errors were encountered:
This makes a lot of sense. Is there any chance you'd be available for a quick Zoom next week to help us better understand your use case and level of urgency of this request? You're welcome to DM me on our public Slack or reach me at jonathan@triggermesh.com.
We worked around the issue using benthos, though that's a bit of a pain.
For us this is not an urgent feature request because we're just experimenting right now. I'm sorry, I don't think I could add much to this in a zoom meeting.
I would like to use the AWSS3 target with a generic S3 service, such as minio.
Would you please consider adding alternative endpoint configuration parameters, other than ARN?
Benthos for example, works with AWS and generic S3 services because it supports being able to independently specify:
Benthos also uses aws.session, but it creates the session with explicit parameters here
Whereas I think triggermesh creates an unconfigured session here
I'm not a go person, so this is just a guess.
Would you please consider allowing optional additional parameters that can be passed use when the
session
object is created, so that the s3 target can be used by other s3 providers?The text was updated successfully, but these errors were encountered: