cli-plugins: fix when plugin does not use PersistentPreRun* hooks #1853
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 regressed in 3af168c ("Ensure plugins can use
PersistentPreRunEagain.") but this wasn't noticed because the helloworld test plugin has it's
own
PersistentPreRunEwhich has the effect of deferring the resolution of theglobal variable. In the case where the hook isn't used the variable is resolved
during
newPluginCommandwhich is before the global variable was set.Initialize the plugin command with a stub function wrapping the call to the
(global) hook, this defers resolving the variable until after it has been set,
otherwise the initial value (
nil) is used in the struct.Signed-off-by: Ian Campbell ijc@docker.com
- What I did
- How I did it
- How to verify it
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)