-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Renderer: Fix regression on callback URL in plugin mode #103787
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
Conversation
evictorero
left a comment
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.
Tested with plugin (http and https) and remote render and works as expected.
I left some comments to improve legibility and discuss posible improvements.
|
The backport to To backport manually, run these commands in your terminal: git fetch
git switch --create backport-103787-to-release-11.6.1 origin/release-11.6.1
git cherry-pick -x d7c554c25e614fd353436aa5db20a0fcb88bcb52Resolve the conflicts, then add the changes and run git add . && git cherry-pick --continueIf you have the GitHub CLI installed: git push --set-upstream origin backport-103787-to-release-11.6.1
PR_BODY=$(gh pr view 103787 --json body --template 'Backport d7c554c25e614fd353436aa5db20a0fcb88bcb52 from #103787{{ "\\n\\n---\\n\\n" }}{{ index . "body" }}')
echo "${PR_BODY}" | gh pr create --title '[release-11.6.1] Renderer: Fix regression on callback URL in plugin mode' --body-file - --label 'backport' --label '' --label 'type/bug' --label 'area/backend' --label 'add to changelog' --label 'area/image-rendering' --base release-11.6.1 --webOr, if you don't have the GitHub CLI installed (we recommend you install it!): git push --set-upstream origin backport-103787-to-release-11.6.1And open a pull request where the |
* Renderer: Fix regression on callback URL in plugin mode * cleanup * refactor to not mutate cfg object * apply review feedback (cherry picked from commit d7c554c)
What is this feature?
In this PR that introduces SSL support for the renderer, we missed that the
RendererCallbackURLwas actually always set insettings.goand this leads to issues for users not needing the SSL support (see grafana/grafana-image-renderer#617).Why do we need this feature?
We never intended the change above to be a breaking change, the image renderer should continue working for all users without any change on their side.
Who is this feature for?
Image renderer users (plugin mode)
Which issue(s) does this PR fix?:
Fixes grafana/grafana-image-renderer#617
Special notes for your reviewer:
Please check that: