Fix for Nucleus Terraform is complaining about missing local IAM policy files if executed multiple times after terraform destroy #134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗒️ Summary
At the moment Nucleus Terraform scripts generates IAM policy files locally before creating the IAM roles. This works well if we only use terraform apply any number of time and then used terraform destroy only once. Executing terraform destroy deletes these locally generated policy files and any subsequent terraform destroy commands complain about missing policy files. There is a workaround for this by using git to restore the deleted placeholder IAM policy files (or manually copy and paste placeholder IAM policy files from template files). But this work around adds manual and confusing steps for someone who does a deployment.
This pull request introduces fully Terraform based IAM policies instead of JSON based IAM policy files, to avoid locally generated IAM policy files.
♻️ Related Issues
#133