-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix(plugin/azure-function): clear upstream uri and request uri inject plugin logic #11850
Conversation
@bungle Hi Aapo, I do not know how this plugin is designed, but I think these upstream URIs and request URIs can not inject azure function plugin logic, Which do you mean? |
bc1121c
to
8a57d00
Compare
changelog/unreleased/kong/fix-upstream-uri-azure-function-plugin.yml
Outdated
Show resolved
Hide resolved
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.
The change seems reasonable to me since concatenating the upstream URI/request URI with the conf.routeprefix
is quite unnecessary, it seems we only need the routeprefix
to construct the Azure API request
Approved although it might be a potential behavior change
changelog/unreleased/kong/fix-upstream-uri-azure-function-plugin.yml
Outdated
Show resolved
Hide resolved
91cea88
to
10a73a8
Compare
10a73a8
to
4aabbd5
Compare
@Tieske Do you happen to know / remember why this plugin concatenated the upstream path? This PR changes the existing behavior. |
@Tieske do you have any further information? |
once upon a time... the tests passed, and I committed... Really, don't recall the details. It mimicked the Lambda one, and I had test functions that worked... |
3631b93
to
efbcdae
Compare
I don't recall anything about this either. |
Is there any further action items here folks? Can we merge it? |
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.
I'm okay with the changes but I think we should make this a "breaking_change" in the changelog, since some users could depend on this behavior
efbcdae
to
d8e5eb4
Compare
@brentos I have changed the entry to breaking change type. Please help me review it again. |
d8e5eb4
to
0a55508
Compare
0a55508
to
1953c64
Compare
Summary
Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdFull changelog
Issue reference
KAG-2841