[Plugin SDK] Implement another way to create plugin #5698
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.
What this PR does:
as title
Why we need it:
In #5693, I wanted to remove the duplicated
Name()
andVersion()
definitions in the Kubernetes plugin.It's easy to remove the duplication in the k8s plugin only, but it's better to provide a way to implement plugins without requiring the
Name()
andVersion()
methods in multiple interfaces.I noticed that we can provide the way that requires name and version as positional arguments when creating a plugin.
In this way, the plugin implementations are passed as the Functional Options Pattern to the plugin constructor function.
Additionally, we can implement assertions to the constructor function to provide helpful errors.
Which issue(s) this PR fixes:
Part of #5530
Does this PR introduce a user-facing change?: