-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
add ctx parameter to provider interface and aws API #1364
Conversation
/assign @njuettner |
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.
This makes sense 👍. I don't really think it is a breaking PR unless you mean other PR's having a merge conflict after merging this PR?
Out of curiosity, which project you're talking about depends on external-dns?
lgtm. Let's wait until we get the current release out before merging this. |
This is a private project. |
/hold cancel |
@tariq1890 Thank you! |
/remove hold |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: njuettner, tariq1890 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
NOTE: This is a breaking change.
Why am I doing this?
i) We use external-dns as a dependency and we are forced to use a private fork since we need to use AWS API calls with context. We'd really like to stop using the fork and have these changes passed upstream.
ii) I think this breaking change is justified since passing contexts down an API call stack is considered a good pattern. This change should also pave way for removing the many
context.TODO()
s in the codebase. This itself is proof that we ought to be passing contexts.Would to get your thoughts and review on this. Thanks!