Operations | Monitoring | ITSM | DevOps | Cloud

CFEngine works by defining a desired state for a given context and converging towards that goal. Given there is no fixed starting point and that the current context might change wildly it can be challenging to succinctly answer the question “What would CFEngine do?”. In Feature Friday: Don’t fix, just warn we saw how an individual promise could be made to warn instead of trying to automatically converge towards the desired state, a granular --dry-run mode.

2025 will continue the theme of powerful business and technological transformation under a never-ending barrage of cyber threats that are spawning faster and evolving in more complex ways than ever. To ward off an increasingly sophisticated community of threat actors, we’ll need to innovate faster than the speed of the threat landscape — but how?

Implicit list iteration in CFEngine is quite a unique and novel feature. Today we look at a practice example showing how lists can improve the readability and maintainability of your policy. A novel feature in CFEngine is how a list variable is iterated when referenced as a scalar ($(variable)). Let’s take a look at a contrived example.

I recently had a conversation with one of our customers at AWS re:Invent that made me rethink the true value of automation. This customer told me, “You’ve automated so much for us that we almost forget about Qovery. Nobody even asks how to do things anymore.” That statement stuck with me.

High-performance computing (HPC) configuration has become paramount for AI workloads. Companies investing in AI workloads often find themselves with predictable problems: Lots of nodes that are hard to integrate and harder to manage together, under-utilized resources, deployment struggles, inconsistent configurations, and drift.

Configuration management tools can help you track and manage changes to systems within your infrastructure, making sure that your software and hardware runs reliably and smoothly.

CFEngine build modules are great for quickly integrating 3rd party policy into your policy set. Module input (not to be confused with inputs in body common control or body file control which are the list of policy files to load) allows you to define values that apply for a particular module as it’s integrated into your policy set. Let’s take a look at a case of extending a module to support input.