jira-matter-bridge icon indicating copy to clipboard operation
jira-matter-bridge copied to clipboard

Mattermost moving to API version 4

Open jasonblais opened this issue 8 years ago • 4 comments

Hey @vrenjith !

First, hugely appreciate you sharing this project back with the world. Fantastic work!

I wanted to let you know about our plans moving to API v4:

To make the Mattermost API web service easier to use and to offer more powerful options for these integrations, Mattermost will be moving to a new API version soon. Highlights include:

  • Fully documented API endpoints
  • More in-depth access to server functionality
  • Wider use of established HTTP verbs
  • Consistent endpoint structures
  • A new and improved Go driver

We plan to release API version 4 on March 16th, with Mattermost server 3.7. While the current API version 3 will be supported until September 16th, we recommend you begin using API version 4 soon after its release.

Contributing

API version 4 is an active and on-going project. If you're interested in helping contribute, please join our Mattermost community instance and the APIv4 channel.

We've prepared a contribution process for APIv4 and a progress tracker for new APIv4 enpoints to help you get started.

We're also open for suggestions on adding new API endpoints to help with your integration.

jasonblais avatar Feb 14 '17 05:02 jasonblais

@jasonblais As this project appears to be dead or dying, we're trying to determine if we need to develop our own solution for webhook translation between various solutions we're currently using. Regarding the API v3 deprecation, is the actual webhook endpoint changing to no longer be slack-compatible, or is this more of a heads-up from a management perspective?

Unless I've misunderstood this project, it's literally translating the json body to something the incoming webhook on mattermost can understand.

nlowe avatar May 31 '17 20:05 nlowe

Thanks @nlowe for the question!

This is more of a heads up that if the integration is using an apiv3 endpoint, we recommend moving to apiv4 endpoints: https://api.mattermost.com/v4/. This should not impact slack-compatibility. And as for this project, I think you're right. It's not using the API endpoints so it shouldn't be affected.

We have a few other integrations listed in our directory here in case helpful: https://about.mattermost.com/community-applications/#privateApps

If you'll build your own solution, don't hesitate to ping me for questions and for sharing the project with others in the community.

jasonblais avatar May 31 '17 22:05 jasonblais

@jasonblais Thank you for the quick response! We will not be developing our own solution at this time as our legal department is still deciding if we are going to go with slack or mattermost. If we end up developing something we'll be sure to share it with the community!

nlowe avatar Jun 01 '17 13:06 nlowe

This projects seems to work without any issues as of today (we are using it with latest MM 3.9.0) and as @jasonblais said, since I am not using any API here, there should not be any problem.

vrenjith avatar Jun 02 '17 07:06 vrenjith