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

[BUG] A module does not respect an aws_route resource logic for additional CIDR blocks (cidr_block_associations). #94

Closed
kksudo opened this issue Sep 12, 2022 · 2 comments · Fixed by #97
Assignees
Labels

Comments

@kksudo
Copy link

kksudo commented Sep 12, 2022

Describe the bug
This module does not create a aws_route for the additional CIDR block as for the requester and for the accepter. An exists logic works only for the primary CIDR block, as the result you can't connect via peering to the additional subnets.

Terraform version: What Terraform version do you use?
Terraform v1.2.4
on darwin_arm64

Module version: What module version do you use?
v5.0.0

Error message:
Please, provide an output of the error message you get.
There are no aws_route resorces for the additional CIDR block of the VPC accepter.

Terraform code that produces the error:
Please, put your Terraform code here. If you don't want to disclose your code, please, describe your use case thoroughly.

module "vpc-peering-management" {
  source  = "grem11n/vpc-peering/aws"
  version = "4.1.0"

  providers = {
    aws.this = aws.requester
    aws.peer = aws.accepter
  }

  this_vpc_id = var.requester_vpc_id
  peer_vpc_id = var.accepter_vpc_id
  tags        = module.tags.all_tags

  auto_accept_peering = true
  from_this           = var.routing_from_this
  from_peer           = var.routing_from_peer
}

Additional context
Add any other context about the problem here.
In this article described this case.
This is implementation of this case in another module from cloudposse/terraform-aws-vpc-peering.

@grem11n
Copy link
Owner

grem11n commented Oct 13, 2022

Thank you for reporting this bug, @kksudo !

Unfortunately, I don't have much time to work on this module at the moment, therefore I cannot provide any ETA for a fix.
However, contributions are more than welcome!

@strangeman
Copy link

Got the same problem too, I will try to look into the code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants