-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ensure logger is provided #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. This does mean we're drifting more from upstream repo. Do we have thoughts on what the longer term plan is for managing that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Just wondering how many differences we're having from the forked repo, and the difficulty to eventually pull something useful from them.
I'm still planning to submit PR's for all of this upstream after I get things tested. |
Thinking about it a bit more, I'm going to remove the renames from this PR since they are unrelated and are likely to cause more conflicts upstream. |
644cce3
to
9896146
Compare
9896146
to
86a04a5
Compare
* Pass logger to the different structs * Use a builder for the AWS services * Use job specific loggers to propagate properties
I started by fixing an issue where the logger wasn't being passed to the two AWS "interface" structs. I created some factory functions to use which should hopefully be more helpful vs the nil pointer crashes I got in dev.
I also did some renames for clarity on the AWS adapters and took a pass for structured logging so logs should have the same properties now.