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
Now, on every plan or apply the resource is "created", meaning the plan shows as if the resource was not existing.
We can set replayable as false, but then running terraform plan or apply doesn't revert the state of the timer, if for some reason its state was altered manually on the system.
I think this is against terraform's spirit. I can understand that provider is maybe not exactly capable of displaying detailed drift of the resources it manages, but here's the bare minimum I would expect:
ansible-playbook --check should be run in terraform plan mode.
Desired state
Case in terraform plan:
resource state has changed: there should be an information in the plan that the resource will be replaced.
resource doesn't exist: there should be an information in the plan that the resource will be created.
resource has not changed: the plan should indicate no changes to this resource
Case in terraform apply:
resource state has changed: run the playbook
resource doesn't exist: run the playbook
resource has not changed: do not run the playbook
Currently what happens:
(with default replayable = true)
Case in terraform plan:
resource state has changed: resource will be "Created"
resource doesn't exist: resource will be "Created"
resource has not changed: resource will be "Created"
Case in terraform apply:
resource state has changed: resource will be "Created"
resource doesn't exist: resource will be "Created"
resource has not changed: resource will be "Created"
The text was updated successfully, but these errors were encountered:
Hello!
Now, on every plan or apply the resource is "created", meaning the plan shows as if the resource was not existing.
We can set replayable as false, but then running terraform plan or apply doesn't revert the state of the timer, if for some reason its state was altered manually on the system.
I think this is against terraform's spirit. I can understand that provider is maybe not exactly capable of displaying detailed drift of the resources it manages, but here's the bare minimum I would expect:
ansible-playbook --check
should be run interraform plan
mode.Desired state
Case in terraform plan:
Case in terraform apply:
Currently what happens:
(with default replayable = true)
Case in terraform plan:
Case in terraform apply:
The text was updated successfully, but these errors were encountered: