-
Notifications
You must be signed in to change notification settings - Fork 23
INFRA-908 Change grafana plugin install logic #991
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
base: stackhpc/2025.1
Are you sure you want to change the base?
Conversation
@technowhizz , please could you placate the naysayers on the upstream PR? It would be good to finish this. |
@technowhizz the upstream PR has been merged. Is this one ready to be merged? |
@Alex-Welsh Once this PR is merged stackhpc/kolla#368 we can go ahead and merge this |
19df53d
to
8c2ac59
Compare
4b976eb
to
712e0b0
Compare
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.
Default should come from Kolla after backport merges
712e0b0
to
85d250f
Compare
92e4c32
to
a6cd02f
Compare
stackhpc/kolla#368 has merged, anything you want to add to this PR? |
354ce09
to
18510a8
Compare
18510a8
to
4b4bf1e
Compare
Changing the way in which we specify grafana plugins to install. This is due to a change upstream which now allows plugins to be installed in an additive method instead of replacing the upstream default plugins [1]. [1] https://review.opendev.org/c/openstack/kolla/+/913184 Co-authored-by: Will Szumski <will@stackhpc.com>
40ced75
to
7ca3e8e
Compare
This PR contains the changes needed to make use of https://review.opendev.org/c/openstack/kolla/+/913184 (if and when it gets merged).
This PR should only be merged if the above patch is in our kolla.