My first #Ansible contribution was just merged.
Now we can properly parse #Samba configuration.
#automation #configmgmt
https://github.com/ansible-collections/community.general/pull/11512
adds parameter delimiters to from_ini filter by gurubert · Pull Request #11512 · ansible-collections/community.general

fixes issue #11506 SUMMARY Adds a parameter to the from_ini file to be able to specify the delimiter used in the INI document. ISSUE TYPE Feature Pull Request COMPONENT NAME from_ini ADDITIONAL I...

GitHub

📬 The next issue of The Determinate Update is almost here! It’s our behind-the-scenes look at how we're advancing Nix, NixOS, and reproducible infrastructure at Determinate Systems, from the tools we build to community initiatives we're driving, and more.

🔗 Sign up to stay in the loop: https://mailchi.mp/909681b61b0f/determinate-newsletter

#NixOS #Nix #ReproducibleBuilds #DevOps #Linux #ConfigMgmt #DeterminateNix

Hey everyone, the very first release of #OpenVox has been released! It’s a drop in replacement for #Puppet and is ready for initial evaluation. Here’s a link to the blog post with more details via #HackerNews in hopes you’ll help vote it is so that even more people know what #VoxPupuli has accomplished 😁

https://news.ycombinator.com/item?id=42786871

[ #OpenSource #ConfigurationManagement #ConfigMgmt ]

The first release of OpenVox is hot off the presses | Hacker News

HowTo: Automated Deployment of FreeBSD VMs in Proxmox with ProxLB and Terraform • gyptazy.com - The DevOps geek

In today's fast-paced IT environments, automation is essential for maintaining efficiency and staying competitive. Whether you're managing a small-scale infrastructure or an enterprise-level system, the ability to deploy virtual machines (VMs) quickly, consistently, and with minimal manual intervention can be transformative. This is where tools like ProxLB and Terraform come into play, offering a powerful

gyptazy.com - The DevOps geek • DevOps, coding, cloud and open source in a geeky way.

I'm genuinely proud to have just finished and published a marquee piece that explains how #CUE makes handling #configuration so much nicer!

It's here, on the main #cuelang site: https://cuelang.org/docs/concept/how-cue-enables-configuration/

If, like me, you really dislike hand-wrangling #YAML and #JSON then please do have a read -- and let me what you think 😁

#config #ConfigMgmt #cfgmgmtcamp #configmanagementcamp #configmgmtcamp #data #schema #schemas #schemata #ConfigFiles #Sysadmin #DevOps #SRE

How CUE enables configuration

Configuration is one of CUE’s core tasks. People often start using CUE because it makes it safer and easier to produce new configuration files and to validate existing files - but its capabilities run deeper. In this guide we’ll begin with the basics of how CUE makes configuration better, and then explore the potential of some of its more advanced features for configuration. Here’s what you’ll find in this guide: Validating existing configuration files Type checking Generating configurations Reducing boilerplate Tooling and automation Abstractions versus direct access

CUE

I only learned properly a couple of weeks back about how elegant #CUE's multi-for-loop construct is!

Because in #ConfigMgmt land we're /so/ often dealing with spiky, nested objects, the nested "for" loop has a lovely indent-saving form: here, the loop starting on L37 incorporates 3 for elements, 1 "if" guard, & 1 additional temporary allocation ("let"), whilst letting me iterate over the /innermost/ elements of a (resource|data).<level1>.<level2> shaped struct 🙂

#cuelang is genuinely awesome!

A #Terraform #IaC #ConfigMgmt straw poll for you:

I need to inject some kind of side-effect-free marker into some (many!) TF config expressions/interpolations.

All 4 of the following 1-line options work, with no performance difference between them.

Please help me by selecting any/all that, if you saw them in a (.tf.json) config, you feel *wouldn't* confuse or annoy you ...

"${ some.expression /* typecheck:number */ }"
33.3%
"${ some.expression }${ /* typecheck:number */""}"
11.1%
"${ true ? some.expression : "typecheck:number" }"
11.1%
"${ try(some.expression, "typecheck:number") }"
44.4%
Poll ended at .