pawelpesz

Any news on this? At the moment the only working configuration when creating multiple VPCs in the same project seems to be the default one: ``` enable_nat_gateway = true single_nat_gateway...

Please disregard my previous comment, the error in question springs up only when the subnet list is empty.

This is still a problem. And a significant one, IMHO.

> only showing the changed set blocks instead of ones that had no change has made this plugin much more usable, solving this issue Exactly, that would be the expected...

@TheQueenIsDead sorry, I misquoted your comment. I would expect a **more concise plan**, instead of: ``` # helm_release.example will be updated in-place ~ resource "helm_release" "example" { id = "my-release"...

I think Andrey meant support for **Origin Access Control** which is now preferred over **Origin Access Identity**. https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudfront_origin_access_control

This is still an outstanding problem.

I believe explicitly setting the `lockfile` option to `false` should make this unwanted discrepancy go away 😄 https://terraform-docs.io/user-guide/configuration/settings/#lockfile