You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't fully grasp the logic behind redeployable = true at the moment, that just recreates the resource every time.
I was expecting that on the second terraform apply, the playbook would run in check-mode and only if ansible reports that changes needs to be made, the ansible_playbook resource would be recreated.
At the moment though, the ansible_playbook is always recreated whether changes needs to be made or not.
This will partially defeat Terraform goal, since under normal circumstances if no change is needed, no resource should be modified.
Also, it produce noise on Terraform logs, making harder to read other resources changes.
Is there a reason why this approach is not followed?
The text was updated successfully, but these errors were encountered:
I can't fully grasp the logic behind
redeployable = true
at the moment, that just recreates the resource every time.I was expecting that on the second
terraform apply
, the playbook would run incheck-mode
and only if ansible reports that changes needs to be made, theansible_playbook
resource would be recreated.At the moment though, the
ansible_playbook
is always recreated whether changes needs to be made or not.This will partially defeat Terraform goal, since under normal circumstances if no change is needed, no resource should be modified.
Also, it produce noise on Terraform logs, making harder to read other resources changes.
Is there a reason why this approach is not followed?
The text was updated successfully, but these errors were encountered: