Update query project when switching datasources #41
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.
What does this PR do?
Adds checks that the configured query projectName matches the current datasource instance projectName configuration. This resolves two current issues:
Closes #33
How does this impact users?
Enables users to install multiple copies of the plugin with different projects configured for each copy. These copies of the plugin can then be used in a dashboard template variable, or to simplify switching between projects in the editor query mode by treating them as different datasources.
What needed to change in the code and why?
Checks on the query projectName were added to the query editor and the datasource
request
handler because the datasource project name can change without the query itself changing.How did you test this?
Locally tested using a template variable setup.
Code review notes
none