aws_instance Changing monitoring argument doesn't change an instance

[robertfirek]

Changing monitoring option in terraform file doesn't change the instance in AWS if the instance already exists.

Plan shows:

~ aws_instance.someinstance
    monitoring: "0" => "1"

During execution everything looks fine

aws_instance.someinstance: Modifying...
  monitoring: "0" => "1"

Unfortunately the EC2 instance remains unchanged and next execution of plan command showing that the instance must be changed and execution of apply command tries to modify this instance again.
_Output doesn't show any errors._

Workaround:
Manually change monitoring settings. State will be refreshed with the right status.

[robertfirek]

Probably this issue and #2700 are concerning the same problem.

[catsby]

Hey @robertfirek thanks for sending this in – I've patched the behavior in #2794

[robertfirek]

@catsby Thank you for your update. I'm waiting for next release 👍

[catsby]

Hey @robertfirek – I just merged this fix, but I'm sorry to say it didn't make the v0.6.1 release (out yesterday) 😦

Hopefully building from master is something you can do, or if not, it will go out in the next release (though I'm not totally sure when that will be).

I apologize for not getting this in there when I said thought I would.

[robertfirek]

That's fine @catsby. When do you plan next release?

[catsby]

It's not scheduled yet... if I were to guess now I would say the first week of July for another patch level release (0.6.2). If it's a larger feature release (0.7) it would be longer, but probably still July

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.