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 \u201cterraform apply\u201d, it would not considers as a changes and terraform would flag no resources addition and change.<\/p>\n\n\n\n
Thus, How to apply a provisioners changes in resources created. There are 2 method to apply provisioners even after \u201cterraform apply\u201d. <\/p>\n\n\n\n
Adding provisioner sections to an existing (already provisioned) aws_instance is not something that terraform notices as a \u2018change\u2019, 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.<\/p>\n\n\n\n
Method 1 \u2013 Destroy and Recreate<\/p>\n\n\n\n
Adding provisioner sections to an existing (already provisioned) aws_instance is not something that terraform notices as a \u2018change\u2019, 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.<\/p>\n\n\n\n
Method 2 \u2013 Using null_resource<\/p>\n\n\n\n
The solution is to create a resource \u201cnull_resource\u201d \u201cnameYouWant\u201d { } and then run your commands inside that. They will run after the initial resources are created:<\/p>\n\n\n\n