-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Regression when S3 secret has trailing newline #981
Comments
icecoffee531
pushed a commit
to icecoffee531/argo-workflows
that referenced
this issue
Jan 5, 2022
* fix(eventsource/resource): return entire event object instead of just event.obj Signed-off-by: Scott Weitzner <scottweitzner@gmail.com> * feat(eventsource/resource): add new filed to pass in old object to ResourceEventData Signed-off-by: Scott Weitzner <scott.weitzner@blackrock.com> * feat(eventsource/resource): for event body refer to event.Obj instead of just event Signed-off-by: Scott Weitzner <scott.weitzner@blackrock.com> Co-authored-by: Vaibhav <vaibhav.page@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
What happened:
Before v2.2.0, we used to trim whitespace from S3 access keys and secret keys. Somehow this got lost with the refactoring to use argoproj/pkg/s3. If there is a trailing newline, S3 operations fail with:
Anything else we need to know?:
Workaround is to trim the trailing newline in the secret
Environment:
The text was updated successfully, but these errors were encountered: