Home
Contribute Contact Us Browse all meetings
Home Contribute Contact Us Browse all meetings
keptn / Keptn Tutorials / 8 Aug 2019
keptn / Keptn Tutorials / 8 Aug 2019
Previous Meeting
Next Meeting
⏯
Add meeting Rate page Subscribe
youtube image
►
From YouTube: Keptn notification Service for MS Teams

Description

See this blog for context of this video. https://medium.com/@robjahn/keptn-now-talks-ms-teams-how-we-expand-keptns-footprint-in-the-microsoft-world-c330c0c8d4f1. This video shares an overview of a new Keptn notification service for Microsoft Teams that myself and Dynatrace colleague, Mike Beemer, developed and how you can install and try it out for yourself.

A

Hi, this is a short video where we can show you how we can set up the new notification service with Microsoft teams, so picking up from the kind of the setup that I have in my blog I do have a captain environment, running version 4, and we have a series of services to allow the deployment of an application with an integration to Microsoft teams. So these instructions here that are listed as step by step kind of summary, or what we're going to show you now in this video.

A

So first we're going to come in here and create a team create a new team will create it from scratch. We'll make it public, let's just call it captain.

A

Once we make our team, we can add members to join, but in our case I'm already a member so I'm going to skip this step and we're going to go ahead and create a new channel and then let's just give this, maybe you call it. Captain notifications. Add that channel.

A

Ok, now we're going to go ahead and add a connector.

A

In this case, we want to add an incoming webhook, so we'll choose that one and we will install it.

A

And let's just go ahead and call this.

A

Captain notifications, actually we can call this captain webhook and we could optionally give it an image, let's go ahead and give it captain and we will create, and what we need to do is save this webblock that it generated we're. Gonna use this web hook for the configuration of the service. Now we are done and if you need to manage this again, we can come into configured, we can see one configured and then we can manage this web look again.

A

So at this point we do have our captain notifications channel as part of our team. Now, let's move on to the step to deploy the captain's notification service, so you can see here I'm in github, and what we can do is take these two files: notification, distributors, Yamma and notification service channel and copy that up into our environment.

A

So here you can see I have these two files here and what we need to do is edit the notification service file and down here, if you notice, there's a URL for Microsoft teams and so we're just simply going to paste in our our web poem URL that we had from the configuration of teams and I will to simply save this and now in order to deploy this into our environment. We can just do. Cube control apply this file and we need to do the distributor's, which is the the service.

A

That's going to be listening to the captain events and then we're going to also install the service and the right name, and now this is here, and so what we can do is monitor this by looking at cube control and we look in the captain namespace and monitor the pods, and so what you should see here is the services starting to be put in place, and we just want to get more time.

A

Okay, so now we have our notification service up, then all the distributors listening for events. Now we can go ahead and let's fire up an event. There's a couple ways it can be done. It can be done directly from the CLI, but why don't I just show you a way we can actually run it from Azure DevOps pipelines using the CLI, so here I have a pipeline created with the bash task and simply I'm configured some parameters to define the URL.

A

My token, my project, my image, I'm downloading the CLI as a step I'm, making it executable I'm going ahead and running the captain off in an automated way and then I'm going to send the image that's defined in my variables here. So if I go ahead and create this release, let's let it run, you can watch the release here and we can watch the logs as it's executing and what we're going to be looking for is the send event to be initially created and to show up in our team service.

A

So if we kind of keeps teams open at the same time, you could probably see it take place almost as soon as the ascend event that takes place up there. You go so here if you noticed I'm already receiving a new artifact event. For my friend service, I've done a configuration change and, let's just look at the logs real, quick, just to see what was happening there. So you know, in my case, I had a URL particular project. I, wanted the fronted image tag number one. You were downloaded the CLI kind of a big download.

A

Then it's decompressing guitar, making it executable authenticating. My CLI successfully authenticated, send my my new artifact event, send a new artifact successfully and now that my pipeline is running I can see here. My new artifact I actually have this cop that captain context ID. So if I am using captain bridge, which is this I can come here and search for that context. Id and I can see you know more details about the log from bridge, but you can see here. You know down to the big bottom.

A

I am sending the new event and it's in the process of deploying the app right now. So, if we continue to monitor this, we will eventually get a deployment complete event and it will do the testing and move on through the various stages. There. We go deployment finished right there and doing deployment into staging configuration change in the staging and so on. So that's that's basically what's happening here. So hopefully you know see how easy that is to set up.