Ensure loaded plugin config is saved to helm server. #6022
Merged
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.
Description of the change
In #5339 we inadvertently switched from an assignment to a short variable declaration:
which meant that, in context, a new
pluginConfig
var was created in that scope, so that the actualpluginConfig
var from the outside scope remained empty.Benefits
Plugin config works again for the Helm plugin.
Possible drawbacks
Applicable issues
Additional information
I spent some time trying to write a test for this, but I could either extract the 5 lines to a separate function and test that or test the
NewServer
function itself. The latter is very difficult because it instantiates a bunch of network requests, and the former seems redundant since we already extract the functionality to thecommon.ParsePluginConfig()
function... it's really just a golang gotcha that is important to be aware of:a := foo
is equivalent tovar a atype \n a = foo
and so is always creating a new variable in that scope.