Conversation
|
Hi @brutto, thanks for your PR and the kind words! The only thing that makes me hesistant is the multiline-configuration. This seems very error-prone. Do you know of another way how there could be a 1 to 1 relationsship between Bot ID and Webhook-URL? |
|
@timkley agree, make it with courage first ))) Update PR: make parse config more robust via check every config value and throw exceptions on error to see it mattermost on save. |
|
@brutto thank you so much, this looks promising! Could you take a look at the workflow failures? My go is not good enough to fix it myself 😅 |
fix input argument misprint from copy-paste
fix erro handling in config
forgot
|
Suddenly go also not my primary =) Add `fmt] into import and refactor error handling from config parser: make it more sence. |
|
The ci checks still fail.. |
|
My suggestion would be to write the config as a json: |
|
@kalimanborges to my knowledge this is not supported in the UI |
|
need this so bad |
|
why not just have a json as the value of the mapping between bot and webhook? |
|
@bclermont |
Excellent plugin, thank you for you job.
Add support multibot (in my case) for testing purposes: production vs staging. In other hands maybe in some cases it will be helpful when mm installation has many bots with different deployment (company with many developer's commands each has it's own bot).