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

Required ipv6 when using ingress_with_cidr_blocks? #14

Closed
anthonydeaver opened this issue Oct 31, 2017 · 4 comments · Fixed by #15
Closed

Required ipv6 when using ingress_with_cidr_blocks? #14

anthonydeaver opened this issue Oct 31, 2017 · 4 comments · Fixed by #15

Comments

@anthonydeaver
Copy link

Not sure if this is the proper place or not, but...
using this bit of code:

module "internal_sg" {
    source = "github.com/terraform-aws-modules/terraform-aws-security-group?ref=v1.1.4"

    name        = "user-service"
    description = "Security group"
    vpc_id      = "${module.vpc.vpc_id}"
    ingress_cidr_blocks      = ["0.0.0.0/0"]
    ingress_rules            = ["http-80-tcp", "https-443-tcp"]

    ingress_with_cidr_blocks = [
        {
            from_port   = 8080
            to_port     = 8090
            protocol    = "tcp"
            description = "User-service ports"
            cidr_blocks = "0.0.0.0/0"
      }
  ]
}

I consistently get the error: Error: module.internal_sg.aws_security_group_rule.ingress_with_cidr_blocks: "ipv6_cidr_blocks.0" must contain a valid CIDR, got error parsing: invalid CIDR address:

I'm not using IPV6, and I'm not including it in the module definition.

Version is terraform 0.10.8.

@aterreno
Copy link

aterreno commented Nov 2, 2017

Yeah I've got the same issue

@antonbabenko
Copy link
Member

Thanks for reporting this bug and that you provided example code (it always saves my time!).

A new version v1.2.0 has been released and it should fix this problem. I have added example into examples/complete/main.tf which shows various use-cases.

@analytically
Copy link

Still seeing this issue.

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants