Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws_launch_configuration enable_monitoring option is not obeyed #2700

Closed
antonosmond opened this issue Jul 12, 2015 · 3 comments
Closed

aws_launch_configuration enable_monitoring option is not obeyed #2700

antonosmond opened this issue Jul 12, 2015 · 3 comments
Assignees

Comments

@antonosmond
Copy link

I have a terraform config for an AWS launch configuration which contains the following line:
enable_monitoring = false
as per the docs:
https://www.terraform.io/docs/providers/aws/r/launch_configuration.html#enable_monitoring
On running terraform apply, the following line appears in the output:
enable_monitoring: "" => "0"
However once the apply has completed and I view the instance in AWS, detailed monitoring is enabled.
I'm running terraform v0.6.0 on Mac OS X 10.10.4

@catsby
Copy link
Contributor

catsby commented Jul 20, 2015

Hey @antonosmond – thanks for reporting this. I just patched this recently and the fix will go out in the next release, which should be in the next few days. The fix was in #2735 , if you're curious.

Thanks again!

@catsby catsby closed this as completed Jul 20, 2015
@antonosmond
Copy link
Author

Awesome stuff thanks for the update! Can't wait for the next release I was
wondering when it would come.
On 20 Jul 2015 17:01, "Clint" notifications@github.com wrote:

Hey @antonosmond https://github.com/antonosmond – thanks for reporting
this. I just patched this recently and the fix will go out in the next
release, which should be in the next few days. The fix was in #2735
#2735 , if you're curious.

Thanks again!


Reply to this email directly or view it on GitHub
#2700 (comment)
.

@ghost
Copy link

ghost commented May 1, 2020

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.

@ghost ghost locked and limited conversation to collaborators May 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants