-
Notifications
You must be signed in to change notification settings - Fork 386
MM-18796 - Add POST /plugins/marketplace
API to redux
#938
Conversation
/plugins/marketplace
API to redux
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.
Some comments below on the purpose of using the store and possibly simplifying most of this PR
@@ -2661,6 +2661,15 @@ export default class Client4 { | |||
); | |||
} | |||
|
|||
installMarketplacePlugin = async (id, version) => { | |||
this.trackEvent('api', 'api_install_marketplace_plugin'); |
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.
I believe we are already tracking this on the webapp here
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.
true. However if someone uses this directly by passing the webapp we'll be missing this event. But don't mind removing it :P
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.
Agreed. We should remove the one in the webapp then.
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.
@marianunez
I'm personally OK keeping both, because once 5.16 is released, our analytics tool will contain this event. However >= 5.18 it'll be the other redux event, it might be hard to put together that data if you need to see how many people installed a marketplace plugin. My suggestion would to keep both now. If this change was going into 5.16 then it would've been fine removing that event.
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.
There still needs to be a change to add the event to the whitelist here so that it can actually get logged - given that most events right now are bypassed to reduce usage in segment.
@aaronrothschild could you confirm if we should include this event to the whitelist to get tracked?
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.
ah. forgot about that as well. Good catch! Maybe i should revert my other webapp change to remove the tracking there? or leave it the way it is right now?
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.
0/5 either way. We just need to make sure that whichever we keep we add to the whitelist so that it actually gets to segment:
ui_marketplace_download
and/or
api_install_marketplace_plugin
@aaronrothschild thoughts?
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.
@marianunez shall we unblock this PR and I can update the tracking events once I get the confirmation from Aaron.
I've created a jira to keep track and I can follow up with Aaron later, does that work?
https://mattermost.atlassian.net/browse/MM-19318
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.
Sure, we just would need to add the new event in the whitelist then because now with ui_marketplace_download
removed from the webapp, we are not tracking either at this point🤔
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.
ah i didn't realize that ui event was whitelisted :(. I've reverted my change in webapp. mattermost/mattermost-webapp@0a5ec12
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.
Changes needed if we want to actually track the event in segment
@@ -2661,6 +2661,15 @@ export default class Client4 { | |||
); | |||
} | |||
|
|||
installMarketplacePlugin = async (id, version) => { | |||
this.trackEvent('api', 'api_install_marketplace_plugin'); |
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.
There still needs to be a change to add the event to the whitelist here so that it can actually get logged - given that most events right now are bypassed to reduce usage in segment.
@aaronrothschild could you confirm if we should include this event to the whitelist to get tracked?
@prapti just a reminder that this will be tested as part of the final testing for the signed plugins epic |
@iomodo * poke * |
oo so fast :P |
too slow :D |
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.
Approving to merge into plugin-signing feature branch. Will be tested once ready for master.
Summary
Add POST
/plugins/marketplace
API to reduxTicket Link
Fixes: https://mattermost.atlassian.net/browse/MM-18796