VCF Operations Orchestrator: Why I Write Actions and Not Workflows (Mostly)
This might be a controversial stance, but if you’ve reviewed any of my VCF Operations Orchestrator code, you’ll notice that 99% of it is written as Actions. I take this approach because it enables me to write “pure” JavaScript code that is easier to read, maintain, and integrate with modern development tools such as linters, unit testing frameworks, and code analysers. Workflows are a visual tool that provides a drag-and-drop interface used to develop automation flows without writing (much) code. It was originally intended for system administrators and infrastructure teams, who might not be traditional developers, to automate tasks on...
