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

update terraform-provider-aws and aws-sdk-go versions #17990

Closed
danbf opened this issue May 3, 2018 · 4 comments
Closed

update terraform-provider-aws and aws-sdk-go versions #17990

danbf opened this issue May 3, 2018 · 4 comments
Labels

Comments

@danbf
Copy link

danbf commented May 3, 2018

please update terraform-provider-aws and aws-sdk-go versions. support for AWS regional WAF is supported there but until the terraform-provider-aws plugin is merged here it's not available
https://github.com/terraform-providers/terraform-provider-aws/blob/master/CHANGELOG.md#1130-march-28-2018

Terraform Version

Terraform v0.11.7

Terraform Configuration Files

resource "aws_wafregional_ipset" "ipset" {
  name = "tfIPSet"

  ip_set_descriptor {
    type  = "IPV4"
    value = "192.0.7.0/24"
  }
}

resource "aws_wafregional_rule" "wafrule" {
  name        = "tfWAFRule"
  metric_name = "tfWAFRule"

  predicate {
    data_id = "${aws_wafregional_ipset.ipset.id}"
    negated = false
    type    = "IPMatch"
  }
}

resource "aws_wafregional_web_acl" "wafacl" {
  name        = "tfWebACL"
  metric_name = "tfWebACL"

  default_action {
    type = "ALLOW"
  }

  rule {
    action {
       type = "BLOCK"
    }

    priority = 1
    rule_id  = "${aws_wafregional_rule.wafrule.id}"
  }
}

Debug Output

Crash Output

N/A

Expected Behavior

terraform should be able to aws_wafregional_web_acl objects

Actual Behavior

aws provider plugin does not support aws_wafregional_web_acl objects

Steps to Reproduce

  1. terraform apply of the example in https://www.terraform.io/docs/providers/aws/r/wafregional_web_acl.html
resource "aws_wafregional_ipset" "ipset" {
  name = "tfIPSet"

  ip_set_descriptor {
    type  = "IPV4"
    value = "192.0.7.0/24"
  }
}

resource "aws_wafregional_rule" "wafrule" {
  name        = "tfWAFRule"
  metric_name = "tfWAFRule"

  predicate {
    data_id = "${aws_wafregional_ipset.ipset.id}"
    negated = false
    type    = "IPMatch"
  }
}

resource "aws_wafregional_web_acl" "wafacl" {
  name        = "tfWebACL"
  metric_name = "tfWebACL"

  default_action {
    type = "ALLOW"
  }

  rule {
    action {
       type = "BLOCK"
    }

    priority = 1
    rule_id  = "${aws_wafregional_rule.wafrule.id}"
  }
}

Additional Context

there is an existing PR to update these: #17901

References

#17901
https://github.com/terraform-providers/terraform-provider-aws/releases/tag/v1.13.0

@tombuildsstuff
Copy link
Contributor

hi @danbf

Thanks for opening this issue :)

The version of the AWS Provider and the version of Terraform Core are related, but can be updated independently. Since 1.13.0 has been released - you can access this by setting this as the version needed in the Provider block, for example:

provider "aws" {
  version = "=1.13.0"
  # ..
}

Once that's set - you should be able to run terraform init which will download the new version and the new features are available. Would you be able to take a look and see if this solves your issue? Since this is a configuration question rather than a bug in Terraform - I'm going to close this issue for the moment.

Thanks!

@danbf
Copy link
Author

danbf commented May 8, 2018

@tombuildsstuff i was getting error's on that when i had something like this set. i can re-produce but the text said something like plugin version 1.1.0,1.13.0 not available.

so is terraform no longer going to update plugins via a mechanism like #17901 ?

provider "aws" {
  version = "1.13.0"
}

@danbf
Copy link
Author

danbf commented Jul 20, 2018

figured out the issue here. had more then one module with a provider version and when they were different versions i got things like 1.1.0,1.13.0 not present

@ghost
Copy link

ghost commented Apr 2, 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 Apr 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@tombuildsstuff @danbf and others