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.

Sign up for GitHub

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

Jump to bottom

Re: Transfer subscription to another plan is not take into account properly in logs #9530

Open

exalate-issue-sync bot opened this issue Feb 20, 2024 · 0 comments

Labels

project: APIM type: bug

exalate-issue-sync bot commented Feb 20, 2024 •

edited

After transferring the subscription to another plan, in the logs the call, it is still linked with the old plan.

To Reproduce :

Logged in as an API owner
Transfer one subscription from plan A to plan B Attachment - image.png
Then go to the subscription, and click on “Transfer”, select my plan B, save (no new deployment are triggered, and the issue happens
The display is good, my sub looks good and linked to plan B
Then when calling the api, with the api key of my sub
Go to overview, logs of the api Attachment - image.png
And seeing that the call is still linked to plan A

Tested in 3.20.26

exalate-issue-sync bot added project: APIM type: bug labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment