3 Commits (2597ef9da271fb89e09152cfe09ee7a8a4cd3415)

Author	SHA1	Message	Date
Martin Atkins	ecca5f291e	vendor: switch to Go modules ... govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.	8 years ago
James Bardin	a0b70b0ec7	Sync the vendor folder with the manifest ... A number of PRs have come through which modified the vendor folder without recording the proper information. This resets everything back to the recorded version.	9 years ago
Martin Atkins	158a90b25b	Grafana Provider, with Data Source and Dashboard resources (#6206) ... * Grafana provider * grafana_data_source resource. Allows data sources to be created in Grafana. Supports all data source types that are accepted in the current version of Grafana, and will support any future ones that fit into the existing structure. * Vendoring of apparentlymart/go-grafana-api This is in anticipation of adding a Grafana provider plugin. * grafana_dashboard resource * Website documentation for the Grafana provider.	10 years ago