aws_lb_target_group.health_check.path is not optional in tf 0.11

[Alexander Lehmann]

Hi,

I had my terraform scripts fail after updating to terraform 0.11 (I assume, maybe it was an update for aws provider I didn't notice) because aws_lb_target_group.health_check.path  is no longer optional and has to be set to "/" to get the old function working again.

Is that intentional or am I making an error somewhere?


bye, Alexander

[Paddy Carver]

Looks like it was part of the 1.3.0 release of the AWS provider. https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#130-november-16-2017

The CHANGELOG indicates it should only affect new resources, not break existing resources. If that's not the case, I'd encourage you to open a bug on the provider: https://github.com/terraform-providers/terraform-provider-aws/issues

Cheers,

Paddy

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to terraform-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/1c3450a5-dcbe-4afb-bd5e-d6d84ae114f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Hodgson]

Hi,

The issue isn't with 1.11 but the AWS provider > 1.3.0 as stated and I can confirm it brakes existing resources.

Actually I haven't managed to get ALB target groups upgraded to the post 1.3.0 schema yet, even after adding the values to the Terraform config, but wanted to wait until raising a bug report in case I was doing something silly.

Each time I run Terraform apply on the resources I get an error from AWS stating that some required fields are missing.

Andrew.
________________________________________
From: terrafo...@googlegroups.com [terrafo...@googlegroups.com] on behalf of Paddy Carver [pa...@hashicorp.com]
Sent: 27 November 2017 17:20
To: terrafo...@googlegroups.com
Subject: Re: [terraform] aws_lb_target_group.health_check.path is not optional in tf 0.11

Looks like it was part of the 1.3.0 release of the AWS provider. https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#130-november-16-2017

The CHANGELOG indicates it should only affect new resources, not break existing resources. If that's not the case, I'd encourage you to open a bug on the provider: https://github.com/terraform-providers/terraform-provider-aws/issues

Cheers,
Paddy

On Mon, Nov 27, 2017 at 5:22 AM, Alexander Lehmann <alex...@gmail.com<mailto:alex...@gmail.com>> wrote:
Hi,

I had my terraform scripts fail after updating to terraform 0.11 (I assume, maybe it was an update for aws provider I didn't notice) because aws_lb_target_group.health_check.path is no longer optional and has to be set to "/" to get the old function working again.

Is that intentional or am I making an error somewhere?


bye, Alexander




--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to terraform-too...@googlegroups.com<mailto:terraform-too...@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/1c3450a5-dcbe-4afb-bd5e-d6d84ae114f8%40googlegroups.com<https://groups.google.com/d/msgid/terraform-tool/1c3450a5-dcbe-4afb-bd5e-d6d84ae114f8%40googlegroups.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to terraform-too...@googlegroups.com<mailto:terraform-too...@googlegroups.com>.
To view this discussion on the web visit https://groups.google.com/d/msgid/terraform-tool/CA%2BBw9CiKHpvK76DfYzGhmUnCCByNY7Lb9mUZ2nathXsuMsv-rw%40mail.gmail.com<https://groups.google.com/d/msgid/terraform-tool/CA%2BBw9CiKHpvK76DfYzGhmUnCCByNY7Lb9mUZ2nathXsuMsv-rw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

[Alexander Lehmann]

I should say that I started with the scripts on the "empty" environment and then it fails (so thats the behaviour described in the changelog)

what threw me off was that its not yet updated in the terraform.io docs (and I didn't check the aws docs)

On Monday, November 27, 2017 at 6:20:47 PM UTC+1, Paddy Carver wrote:

Looks like it was part of the 1.3.0 release of the AWS provider. https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#130-november-16-2017

The CHANGELOG indicates it should only affect new resources, not break existing resources. If that's not the case, I'd encourage you to open a bug on the provider: https://github.com/terraform-providers/terraform-provider-aws/issues

Cheers,

Paddy

On Mon, Nov 27, 2017 at 5:22 AM, Alexander Lehmann <alex...@gmail.com> wrote:

Hi,

I had my terraform scripts fail after updating to terraform 0.11 (I assume, maybe it was an update for aws provider I didn't notice) because aws_lb_target_group.health_check.path  is no longer optional and has to be set to "/" to get the old function working again.

Is that intentional or am I making an error somewhere?


bye, Alexander

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/terraform/issues
IRC: #terraform-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Terraform" group.

To unsubscribe from this group and stop receiving emails from it, send an email to terraform-too...@googlegroups.com.