Great read with my morning coffee 🙂 This one: "...a one-off policy change to solve an urgent problem. The environment keeps working until six months later, when nobody remembers why that one component behaves differently, and a routine patch or rebuild turns into a guessing game." struck a cord here. Telstra learned that the hard way when they laid waste to most telecom in Australia a few weeks back. As you write, but in their own words: “We now believe this occurred because of an intentional design change that had previously been made to the equipment to fix an earlier fault [which] had not been properly documented,” the submission states. “This meant the maintenance team was not aware of the way the device would behave when restarted.” IaC is definitely among the most interesting mainstream concepts these days. Another cool thing about Terraform and Ansible is that you, as on engineer, free yourself from vendor lock-in, i.e. none of those are inherent to Citrix or any specific public cloud. Learning Terraform and Ansible are universally applicable, so if your employer decides on a different EUC vendor, you're still in the game. Also interesting to note how "export to Terraform" buttons start showing up everywhere in the Citrix DaaS console etc.

I was truly surprised to see that Omnissa and Parallels don't offer a Terraform or Ansible library. Citrix has certainly jumped in with both feet. There's a nsconf2iac as well that converts your NetScaler configuration to a Terraform file or Ansible playbook.