-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add plugin helper functions #951
Conversation
0769d3d
to
2263851
Compare
2263851
to
f9070a8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ParseCommand
+ MergeConfigs
helpers could be useful, but I think the other ones don't belong here. They doesn't seem to be generic enough, and also use some shortucts like harcoded paths or modifying envs for current process. The DownloadDependencies
will be not necessary anymore on Feburary 6th so I wouldn't keep it as official helper.
I think the solutions you provided are totally fine for the example executor purpose, so let's move most of the code there. In pluginx
I would put something we actually use for our plugins.
We can discuss it offline, but please see my comments first 👍
e9799c2
to
2777f11
Compare
2777f11
to
ba5c5d1
Compare
I applied all fixed discussed offline. Once this PR will be merged, I will update our tutorials |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👌 Good work!
Description
Changes proposed in this pull request:
They should simplify Botkube plugins development. First use: https://github.com/kubeshop/botkube-plugins-template/pull/7/files
(Some functions are opinionated as a given approach is required, e.g.
ParseCommand
)I created it for 2 reason:
gh
is more readable as we focus more on the core logic instead of some repeatable work like downloading or running binaries.However, if @botkube-dev you think that is sth that shouldn't be in our repository. I will extract that to a separate one under my GitHub handle.
Related issue(s)
#925