The chef, file, local-exec, puppet, remote-exec, provisioner invokes a script on a remote resource only after it is created. Thus, if you add provisioner code after “terraform apply”, it would not considers as a changes and terraform would flag no resources addition and change.
Thus, How to apply a provisioners changes in resources created. There are 2 method to apply provisioners even after “terraform apply”.
Adding provisioner sections to an existing (already provisioned) aws_instance is not something that terraform notices as a ‘change’, so the provisioner is not run during the next apply. The only way to run the provisioner is to destroy the instance and let terraform create it again.
Method 1 – Destroy and Recreate
Adding provisioner sections to an existing (already provisioned) aws_instance is not something that terraform notices as a ‘change’, so the provisioner is not run during the next apply. The only way to run the provisioner is to destroy the instance and let terraform create it again.
Method 2 – Using null_resource
The solution is to create a resource “null_resource” “nameYouWant” { } and then run your commands inside that. They will run after the initial resources are created:
Email - Contact@DevOpsSchool.com
I can help in the following:
- DevOps - DevSecOps - SRE
- Continuous Integration & Delivery
- Continuous Deployment & Inspection
- Technical Debt Reduction
- Containerization/Micro Services Using Kubernetes & Docker
- Cloud Migration using AWS-Azure-GoogleCloud
- Enterprise observability
- Terraform Tutorials Demo Video - May 16, 2022
- 12 Tips To Successfully Market Your Blog On Instagram - May 16, 2022
- Best Pubs, Bars & restaurants in Pune - May 14, 2022
