Operations | Monitoring | ITSM | DevOps | Cloud

So you’ve just been tasked with creating a Terraform Provider (or maybe upgrading an existing one). As you do your research to prepare for the project, you slowly begin to realize, “well this looks like I’ll just be developing a Terraform specific wrapper for a client of my API.” It’s not particularly difficult, but it seems tedious. Is there a better way to build this? Maybe something that can be modular and automated? A way that’s actually stimulating to implement?

Another post inspired by our weekly internal enablement office hours [should we open this up to the public?] and a few conversations at DevOps Days Atlanta, talking about the experience with Kubernetes can reverberate some sighs. Though in our weekly enablement office hours, the blunt question was asked “well why is Kubernetes so difficult?”. Industry thought leaders would state that Kubernetes is a platform to build other platforms.

London, 21 April 2022. Canonical Ubuntu 22.04 LTS is now generally available, featuring significant leaps forward in cloud confidential computing, real-time kernel for industrial applications, and enterprise Active Directory, PCI-DSS, HIPAA, FIPS and FedRAMP compliance – raising the bar for open source from cloud to edge, IoT and workstations.

If you’re an engineer, it’s probably easy enough to appreciate the technical value of DevOps. DevOps makes software delivery faster, increases agility, improves collaboration and more. That being said, this is likely not the case for business professionals. They don’t always see the value of DevOps as clearly from their perspective. After all, even if you adopt the best DevOps tools and design optimal DevOps processes, there’s no guarantee that DevOps will drive business value.

StackState competes in a crowded market, and “getting found” by potential customers is a major challenge. One of the tactics we initiated recently was to raise our profile on G2, a popular website focused on end-user reviews of many different categories of technology offerings.

Organisations of different scales and forms want to harness the power of data to identify new business opportunities and improve current business operations. Organisations that use data effectively can hold a potential advantage – the ability to make faster and more informed business decisions. However, working with data can be a long-standing problem for businesses and functions, especially in data management and software development.

It was clear that reality had begun to shift, and that what once would have been horrifying — the outpouring of rage against a backdrop of constant, low-grade mistrust — had become the new normal. This is how the author of the New York Times described the stories of the irate customer behaviour that started showing in the time of pandemic.

During the past two weeks, our Frontend and Backend teams were busy bees 🐝 with a particular sprint dedicated to bug hunting �� and improvements! Yes, both of the two weeks sprints were dedicated to bugs and improvements ONLY: tracking them, then solving them; gotta catch ‘em all 🚀

Containers are great for developers, but containers are also an excellent way to create reproducible, secure, and portable applications. Applications can be deployed reliably and migrated to multiple computing environments quickly using containers. It could be the developer's laptop to the testing environment or staging to the production environment. To use Dockers, Kubernetes, etc., it has been necessary to build containers.

Before continuous integration was invented, developers had to work on code separately before merging it into the end product. This technique had a high chance of error. If something was left out, it took time to determine the problem. Furthermore, communication between team members became difficult as the project grew. The larger the project, the more developers, engineers, and project owners were supposed to be faithful to each other’s schedules.