This repository was archived by the owner on Mar 17, 2021. It is now read-only.
Add organization ID to client connection using header. #62
+10
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This seems like the right place to do so - the resource API calls that
require an organization ID that are not-quite RESTful also would need
authentication with a user that is an administrator for the
organization. So putting it in at this level works out, and also avoids
adding orgID parameters all over the place.
Co-authored-by: hansnqyr luke@nqyr.io
This is a prelude to a PR on terraform-grafana-provider to fix this issue. It is similar to previous work under this PR: https://github.com/terraform-providers/terraform-provider-grafana/pull/60 - though the change in that PR is not what will result (it's far simpler).