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

Adds wait_for_ready_timeout option to aws_elastic_beanstalk_environment. #5967

Merged

Conversation

dharrisio
Copy link
Contributor

We have found that some of our Elastic Beanstalk Environments take longer than 10 minutes to reach a 'ready' state. This option allows the timeout value to be configured in the terraform document.

Example Terraform document:

provider "aws" {
  region = "us-east-1"
}

resource "aws_elastic_beanstalk_application" "default" {
  name        = "tf-test-name"
  description = "tf-test-desc"
}

resource "aws_elastic_beanstalk_environment" "default" {
  name                   = "tf-test-name"
  application            = "${aws_elastic_beanstalk_application.default.name}"
  solution_stack_name    = "64bit Amazon Linux 2015.09 v2.0.4 running Go 1.4"
  wait_for_ready_timeout = "15m"
}

@stack72
Copy link
Contributor

stack72 commented Apr 1, 2016

Hi @dharrisio

Thanks so much for the PR - this looks good :)

make testacc TEST=./builtin/providers/aws TESTARGS='-run=TestAccAWSBeanstalkApp'
==> Checking that code complies with gofmt requirements...
go generate $(go list ./... | grep -v /vendor/)
TF_ACC=1 go test ./builtin/providers/aws -v -run=TestAccAWSBeanstalkApp -timeout 120m
=== RUN   TestAccAWSBeanstalkApp_basic
--- PASS: TestAccAWSBeanstalkApp_basic (8.06s)
PASS
ok      github.com/hashicorp/terraform/builtin/providers/aws    8.075s

@stack72 stack72 merged commit c10c1b9 into hashicorp:master Apr 1, 2016
terraformbot pushed a commit that referenced this pull request Apr 1, 2016
[origin/master] Merge pull request #5967 from dharrisio/f-aws-elastic-beanstalk-timeout-config
c10c1b9
@ghost
Copy link

ghost commented Apr 26, 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 26, 2020
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 this pull request may close these issues.

2 participants