 which is this one. Can you hear me? Cool. So thanks, everybody, for coming to the last talk. It's been a long day, so I really appreciate that you all come here to still listen to me and talking about CLI plugins. And since I only have five minutes, let's jump right in there. Who here is using CLI plugins already? And who has more than 10 CLI plugins installed? So I hope I'll inspire you all to go home and install all the CLI plugins, because they are pretty done awesome. So first, what are CLI plugins? Let's quickly clarify that. They are small, little binaries that you have available locally that add functionality to your CLI. They are typically written in Go because they have to communicate with the main CLI process over RPC. And that's just the easiest if you do that over Go. This is what it looks like on my local machine. You can see some of the CLI plugins. I have many, many more. You can see some of the CLI plugins that I have installed. And what that does, you see all the marked in red here are all the extra commands that I get from installing a CLI plugin. So you might ask, no, hey, Johanna, say, how did you get all these great CLI plugins? Let me tell you. You just go to this URL. And if you go to this URL, you'll see this website, which is basically a list of a bunch of available CLI plugins. There are many more. There are some CLI plugins that are available on GitHub. And you really have to go hunt them down and find them. But this is a good comprehensive list that will get you started. And this is a time for me to make a quick confession. I subtitled the talk, Extending CLI, Extending Cloud Foundry for Fun and Profit. This is all available for free, right? So you actually will not be able to make a profit. So I just lured you in here thinking that you'll get rich writing CLI plugins. But so I'm going to change the talk to Extending Cloud Foundry for Fun and just general awesomeness, right? So how do you install all these plugins? So there are lots of them available. We just saw that. How do you install them? Two very simple commands. First, make sure you are using the correct plugin repository. You can use your own plugin repository. The CF community plugin repository is the one that I just told you. That's the one where we have the most CLI plugins. But you can write your own repository if you have some plugins that you only want to make available to your organization. And then CF install plugin to install a plugin from that repository. You can also use the install plugin command to install a local binary. Or you can give it a HTTP URL if your plugin is sitting somewhere. So there are lots of ways to install a plugin. Now that we know how to install them, I want to give you some inspiration on which plugins you actually want to install. And so the first one is the most important one. You all know this, right? You're working with Cloud Foundry, and you're trying to push an app, and it's somehow not working. It's not coming up. You have an issue. You have a bad day. You really are sitting in front of your computer, swearing it, and want to throw your keyboard against the wall. That's exactly the situation for which I wrote this plugin. CF tell me a joke. It's kind of like the one thing that hopefully will lighten up your day a little bit. It's the plugin that's on my GitHub. I'll publish it at some point. But yeah, you can use this to help you a little bit. On a more serious note, I think the coolest plugin to me is CF top, which shows you all your applications and how they're doing on Cloud Foundry. Equally cool is CF local, which allows you to compile your local application into a Docker container and run it there, which is cool if you have issues with build pack and you want to do some build pack debugging. So this allows you to do it all locally, and you don't have to push it up to your Cloud Foundry. The first plugin I always install is an update CLI plugin. It allows me to always keep my CLI up to date with a simple command. And then if you are interested in blue-green deployments, serodontan deployments, there's a bunch of them. Everybody thinks it's a cool thing to write a blue-green deployment plugin. I might write one at some point, too. But here's also a list of some available already. And there's so many more, some to connect to your services, easily connect to your MySQL databases, some to work with different Cloud Foundry environments if you have them. CF Open is sweet to just very quickly open a browser with your application in it, and many, many more. But there's always a case when you really want to write your own CLI plugin. And believe me, that's not that difficult. It's actually pretty done easy. The API is well thought through and well documented. And there are use cases where you really want to write your own plugin, especially if you have a bash script that looks like this. I wrote this. I really am ashamed. And you want to turn this into something that looks more like this. So you go from ugly, untestable, unextendable bash to a nice CLI plugin that is written in Go that you can test and extend. That's exactly when you want to write your own CLI plugin. Other use cases for writing your own plugin, if you want to make sure you integrate well with your own services, for example, if you have Prometheus and you want to link from an application straight to Prometheus dashboard, or you want to make sure that your applications are nicely integrated in your Jenkins pipeline. So there are lots of use cases where you really would make sense to write your own. If you just want to make sure that your users have a better time using Cloud Foundry, it's easier for them. There are many use cases where you can write your own plugin. And if you just want to be generally awesome, that's also when you want to write a plugin. And with that, thanks for coming. Enjoy the day tomorrow, and enjoy the festivities tonight, and wish you all a good evening. Bye.