Infrastructure as Code in Large Scale Organizations

The adoption of tools for the provisioning and automatic configuration of "Infrastructure as Code" (eg Terraform, Cloudformation or Ansible) reduces cost, time, errors, violations and risks when provisioning and configuring the necessary infrastructure so that our software can run . However, those who have begun to make intensive use of this technology at the business level agree to identify the emergence of a very critical problem regarding the orchestration and governance needs of supply requests: -Security: How can I control who can create or modify the infrastructure of each environment? -Auditability: WHO made that change, WHEN, HOW and WHY? -Configuration Management: How can I manage the specific configurations of each environment, knowing at all times what values ​​were assigned to each parameter for a given environment? How do we manage secrets? -Scalability: How can I manage the hundreds or thousands of scripts I have in my organization, ensuring that the correct one is always executed and in its latest version, based on the change you want to make? How can I manage dependencies between organization-wide change requests? -Integrity: Why do I have to use two completely different approaches to provision infrastructure and deploy software on that infrastructure? How do I integrate both flows as if they were one? -Compliance: How can I guarantee that the corporate process defined for dealing with supply requests is followed, guaranteeing that all necessary approvals are obtained or that the CMDB is always kept up-to-date? How can I continue to apply advanced provisioning patterns? -Visibility: How can I get immediate information on the status of a provisioning request, Learn how XL Release and XL Deploy responds to all these problems and many more, allowing you to continue working with your favorite tools.