c7290b7ffe
This removes the tests that query the Grafana API for checking whether the prometheus datasource has been provisioned and for checking the number of active dashboards against the number of expected dashboards determined via the chart's values.yaml. The reason for removing these is that Grafana can be configured to use data source types beyond just Prometheus and additional dashboards can be added to Grafana via the Grafana UI. In cases where dashboards are added via the Grafana UI, they are persisted in the grafana database which will cause helm test failures during upgrade scenarios. Now that we have selenium tests executed as part of the Grafana helm tests that validate Grafana is functional, these API tests add little value Change-Id: I9f20ca28e9c840fb3f4fa0707a43c9419fafa2c1 Signed-off-by: Steve Wilkerson <sw5822@att.com>
Openstack-Helm-Infra
Mission
The goal of OpenStack-Helm-Infra is to provide charts for services or integration of third-party solutions that are required to run OpenStack-Helm.
For more information, please refer to the OpenStack-Helm repository.
Communication
- Join us on Slack - #openstack-helm
- Join us on IRC: #openstack-helm on freenode
- Community IRC Meetings: [Every Tuesday @ 3PM UTC], #openstack-meeting-4 on freenode
- Meeting Agenda Items: Agenda
Launchpad
Bugs and blueprints are tracked via OpenStack-Helm's Launchpad. Any bugs or blueprints filed in the OpenStack-Helm-Infra Launchpad will be closed and requests will be made to file them in the appropriate location.