Change grafana plugin install logic

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>

Author: 2 people

etc/kayobe/kolla.yml

@@ -358,9 +358,6 @@ kolla_build_blocks:
   bifrost_base_header: |
     ADD additions-archive /
     ENV TOX_CONSTRAINTS_FILE=/requirements/upper-constraints.txt
-  grafana_plugins_install: |
-    RUN grafana-cli plugins install vonage-status-panel \
-        && grafana-cli plugins install grafana-opensearch-datasource
   ironic_inspector_header: |
     ADD additions-archive /
 
@@ -373,6 +370,8 @@ kolla_build_blocks:
 kolla_build_customizations_common:
   bifrost_base_pip_packages_append:
     - /additions/*
+  grafana_plugins_append:
+    - vonage-status-panel
   ironic_inspector_pip_packages_append:
     - /additions/*
   magnum_base_pip_packages_override:

releasenotes/notes/grafana-plugin-install-logic-d935846abf0d27d0.yaml

@@ -0,0 +1,8 @@
+---
+features:
+  - |
+    New logic for installing grafana plugins. When building you can pass a
+    variable ``grafana_plugins_append`` that contains a list of plugins you
+    want to install. This will be appended to the default list of plugins. The
+    existing method of overwriting the ``grafana_plugins_install`` block still
+    works.