SWEAGLE WANTS TO RID THE WORLD OF BAD CONFIG DATA
SO SOFTWARE APPLICATIONS CAN ENJOY MORE UPTIME,
LESS ERRORS & BETTER SECURITY
config data matters
Firstly, Sweagle wants to bring some order to config data. Secondly, it's on a mission to get rid of all the bad config data swarming around the application estate.
Eat config for dinner
Sweagle eats config for dinner. That’s why config has been given a permanent seat at the table. In the past, config has lived outside of the CI/CD world mainly because its job is to be configurable. It’s doing what it says on the tin.
But with modern DevSecOps, it’s totally acceptable to give multiple people access to make changes on the fly. And why wouldn't you, right?
It’s a bit like Batman
(if you think about it)
Batman showed that jumping from buildings, wearing a mask and living outside the law was acceptable. Not only acceptable - quite normal.
So, in this new vigilante era, the ability to change and challenge the status quo has become more difficult. People have accepted a new norm, processes have deviated, controls have been missed. And so the continuous change continues. Minor escalation becomes slightly bigger... and repeats.
So, think of config data like Batman. It's there to allow easier change,
quicker change, better change. But we still need a process to manage
let's get rid of bad config
So if we allow change to exist outside a release process, it means we don’t see what's changing. We rely entirely on good humans doing good things. Very honorable. But being human, we all know that mistakes, oversights and mishaps are par for the course.
So join Sweagle on the mission to rid the world of bad config data. Sweagle would love to hear from you and promises not to make you wear a lycra suit.