As a member of an operations team that uses infrastructure as code (IaC) practices, you are tasked with making a change to an infrastructure stack running in a public cloud.
Which pattern would follow IaC best practices for making a change?
As a member of an operations team that uses infrastructure as code (IaC) practices, you are tasked with making a change to an infrastructure stack running in a public cloud.
Which pattern would follow IaC best practices for making a change?
As a member of an operations team using infrastructure as code (IaC) practices, the best approach to making changes in an infrastructure stack running in a public cloud involves using version control systems. Submitting a pull request and waiting for an approved merge ensures that all changes are reviewed and approved in a controlled manner, following a collaborative workflow. This process guarantees that the changes are tracked, auditable, and can be rolled back if necessary, which is crucial for maintaining the integrity and reliability of the infrastructure.
E. Submit a pull request and wait for an approved merge of the proposed changes. As a member of an operations team that uses infrastructure as code (IaC) practices, the best practice for making a change to an infrastructure stack running in a public cloud is to submit a pull request (PR) and wait for an approved merge of the proposed changes. This approach follows the best practice of using version control for infrastructure code and collaborating through pull requests to review and approve changes. By following this process, changes to the infrastructure stack are tracked, reviewed, and approved in a controlled and auditable way.
Following IaC best practices, the recommended pattern for making a change to an infrastructure stack running in a public cloud would be to submit a pull request and wait for an approved merge of the proposed changes. This approach allows you to use version control and review processes to ensure that changes to the infrastructure are carefully reviewed and tested before being applied. It also allows you to track changes over time and roll back any problematic changes if necessary. Option A (cloning the repository and running the code) is a good first step, but it does not address the need for review and approval of the changes. Option B (using the public cloud console) is generally not recommended, as it bypasses the version control and review processes that are central to IaC best practices. Options C (making the change programmatically via the public cloud CLI) and D (making the change via the public cloud API endpoint) are both more in line with IaC best practices, as they allow you to automate the process of making changes, but they still do not address the need for review and approval of the changes.
We should follow CI/CD best practices, the answer is E.
The best practice is PR (Pull Request)
It's E
CI-CD best practices recommend pull requests i.e. merge the branch to main, in order to run a pipeline request - which kicks off a terraform deploy
So Answer E