You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The provider sets a header "Grafana-Terraform-Provider" to "true", similar to using a user agent, so that endpoints it calls can provide special treatment if necessary. It would be nice to know the version of the provider so backends can provide specific messaging based on version, including things like:
"version is not supported. upgrade to XYZ"
including or hiding fields or data that cause known breakages in the provider
structure translation in the API after a migration in the backend that changes structure.
I would suggest one of two approaches:
Add a new header that includes the version
Change the value set for "Grafana-Terraform-Provider" to the version of the provider.
Working with a blank slate, I would go for the second approach because it reduces the total number of headers, but if we stop using "true" it's possible that some backends depend on that exact value and would break. So I'd lean towards adding an additional header if this feature request is accepted.
The text was updated successfully, but these errors were encountered:
Feature Request
The provider sets a header "Grafana-Terraform-Provider" to "true", similar to using a user agent, so that endpoints it calls can provide special treatment if necessary. It would be nice to know the version of the provider so backends can provide specific messaging based on version, including things like:
I would suggest one of two approaches:
Working with a blank slate, I would go for the second approach because it reduces the total number of headers, but if we stop using "true" it's possible that some backends depend on that exact value and would break. So I'd lean towards adding an additional header if this feature request is accepted.
The text was updated successfully, but these errors were encountered: