 So, next up, we have, although we're running a little bit ahead of schedule, Matt, so it's not at the time that you posted on Twitter, but Matt Curry is going to join me, the Director of Cloud Engineering at Allstate, to talk a little bit about safety first. Did you pick this song? Yeah. How's it going? That's a good song. If you're all wondering what the joke is, this is a, oh, you changed it. Sorry. Yeah. We had to change the slide. Last minute change. Apparently, his comps team did not approve the first one. Yeah. So, I had a picture of my daughter standing next to a giant pile of fireworks, and they weren't, like, so excited about that, which is fine, because we're all about, you know, tight feedback loops and adjusting on the fly. But I wanted to talk about this idea of deploying with safety in the parallel of kind of firing off fireworks, right? So we have a number of occasions throughout the year, depending on the country that you're from where we enjoy fireworks. And they're beautiful, and if done by professionals, they can be well-choreographed, and they, we all enjoy them, right? And if you watch, like, YouTube channels, you can also see that they can go terribly wrong. And so it's important that we have the right precautions in place in order to ensure that we enjoy these things with safety. And using the structured platform, LightCloud Foundry, we at Allstate have created an environment where our developers can move quickly, but they do so with safety. And so when you think about this metaphor of your workload to, like, different types of fireworks, you have, like, the sparklers, I might let my kids play with the sparklers, and you have, like, the box you get from Costco, which, like, my neighbor was really excited about this year, so he's, like, and that was actually the picture was the used box with, like, everything in it. It was bigger than his child. It was taller than her, which is fine. I mean, and we shoot them off in the street, and, like, that's a little more dangerous. Probably not going to let the kids, like, light the fireworks, right? That would be bad, and irresponsible. And then you have, you know, the crazy, like, everybody has the crazy neighbor. Like, everybody's got one, right, and this is the person that invariably ends up on YouTube, like, goes to the back of the house and, like, pulls out this giant pipe and is, like, it says mortar shell on it, and you're, like, that sounds like a weapon, not, like, like, something that I'm going to enjoy in my backyard, so please, like, keep that away from my children, my house, like, all things. When they're down the street. Yeah, and we all run, like, workloads like that. Like, usually it's, like, innovation or something to that nature, where it's, like, we just want to do the craziest thing you could possibly think of in the name of innovation, and it will be fine. And we have to have these environments that provide safety mechanisms to our developers and to our enterprises so that we can be sure, like, the crazy person doesn't ruin it for everyone. Or maybe just a moderately less than sane person. Yeah. With a really great idea that might work and it might not. Might work and might not. But, you know, the point kind of being is, you know, like the fireworks, the different workloads carry different levels of risk. So if things go wrong, the impact to customers might be different, depending on what it is. And so what we've done at Allstate is we've open sourced a piece of software called Deployed Actile, which is really hard to pronounce. Tell me a little bit about that name because I keep getting hung up on the name. Yeah, me too. I haven't figured out how to spell it yet still. We've released it like a year ago. But it was about the only thing, like, we went through about 100 names with legal and it was just, like, used, used, like, too close to this. And so finally we were like, okay, what are, what is the craziest off the wall name we can possibly come up with to get through approval so that we can open source it? Because nobody here's ever done that. Never, I'm sure. And so that's the name and Andy's going to be talking about that on Friday. So if you want more detail on how we're kind of doing this safe environment, then you can go check out the details of his sessions and he's going to talk about Deployed Actile. But the core thing is there are certain pieces that need to be in place when our developers deploy to Enterprise Cloud, right? So for example, we don't want developers making changes in production or anyone making changes in production for that matter without a change record. You talk about exploding things in the air mixed with alcohol. That sounds bad. Like, who needs gravity? Sounds bad. What could possibly go wrong? What could go wrong? You talk about making changes in production without change control. Also sounds bad. Turns out people do both. So we want to ensure that in our environment we have safeguards to make sure that our teams are acting, fulfilling their obligations in terms of what we require of them, whether it be audit compliance, regulatory compliance, having artifact traceability. And so we've used Deployed Actile basically as this eventing system that emits events as we deploy to our different Cloud Foundry environments. And what it enables our developers to do is think about I want to deploy to production, I want to deploy to UAT, I want to deploy to pre-production. And each of those can actually be multiple Cloud Foundry environments. So for example, production runs across multiple regions. We don't really want our developers to have to think about like, I want to deploy to Region A and Region B and Region C because I need that level of redundancy. We just want them to think about, I want to push to prod and enable them to deal with that at that level of abstraction. And one of the challenges we had when we first created it is, as the platform operators and infrastructure folks, we were like, this is great, people will totally want to use this. And our developers were like, I have like 400 lines of gravy and like a gradle script, it's fine. Totally fine. Totally fine. And we're like, it's not fine to us. And so we had to create an incentive for them to actually use to play Dactyl. And so what we did is using the event system, we were able to basically take the change record and automate that as a part of production deploys so that the developers could just deploy through the CI pipeline. And the change record is all automatically cut validated, like all the Cloud Foundry logs from the different environments get sucked into it. And we mark the change as successful or an unsuccessful. And developers were like, wait, if I use this, I don't have to cut change records? As it turns out, they don't really like doing change records. Who knew? And so that's how we got people to start using it. And then we started attaching additional functions onto that. So now we're using it to test things like, did you deploy this into a lower environment before deploying it to prod, or have you had a vulnerability scan? So we're using it to tie into what Molly just talked about, shift security to the left. And now making sure that those vulnerability scans, the developers no longer have to worry about going into those tools, configuring them, configuring their access, setting all of that up. Instead, they deploy. And all of that stuff happens. And then they get a nice little message after the deploy that says, hey, we've submitted this workload for a vulnerability scan. If you want to look at the results, then here's where you will find them. And it really takes a lot of this toil out of their hands and enables them to move with speed and safety. Safety first. Yeah, so at all state, we protect our customers from life's uncertainties. The way that we can think about this is we're trying to protect our developers from deployment uncertainties or life's uncertainties. Nice tie-in with the company brand. I like that. Hey, that's what we're here for. Well, that is so awesome. And so we're going to talk about it later this week to show how to use it. Is it available in open source? It is. It's on GitHub. We'll post the link. And Andy has a reference to the link in his talk as well. But yes, you can download it and play with it. We'd love the feedback. Definitely start if you get an opportunity. We love to try and get the community more and more engaged with that. We think it's a problem that not just we have, but that others would benefit from our solution. So the more that we can share, the better. That's awesome. Thank you so much, Matt, for coming and sharing this with us today. Thank you.