Plugin Framework: Fix Configure function
#1487
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closes #1485 I was using the `Configure` function of resources to extract the grafana client Turns out that this function is called before ProviderData is even initialized in real world scenarios I moved the client exist check down to where the client is actually used and now the resources work as shown in the modified integration test which used to fail before the fix
|
In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically. |
K-Phoen
approved these changes
Apr 16, 2024
julienduchesne
deleted the
julienduchesne/fix-plugin-framework-resources
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #1485
I was using the
Configurefunction of resources to extract the grafana clientTurns out that this function is called before ProviderData is even initialized in real world scenarios
I moved the client exist check down to where the client is actually used and now the resources work as shown in the modified integration test which used to fail before the fix