provider/aws: Increase Beanstalk env 'ready' timeout

[radeksimko]

This is to address the following test failure:

=== RUN   TestAccAWSBeanstalkEnv_basic
--- FAIL: TestAccAWSBeanstalkEnv_basic (606.92s)
    testing.go:280: Step 0 error: Error applying: 1 error(s) occurred:
        
        * aws_elastic_beanstalk_environment.tfenvtest: 1 error(s) occurred:
        
        * aws_elastic_beanstalk_environment.tfenvtest: Error waiting for Elastic Beanstalk Environment (e-jpqtfzywmh) to become ready: timeout while waiting for state to become 'Ready' (last state: 'Launching', timeout: 10m0s)
    testing.go:344: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error applying: 1 error(s) occurred:
        
        * aws_elastic_beanstalk_environment.tfenvtest (destroy): 1 error(s) occurred:
        
        * aws_elastic_beanstalk_environment.tfenvtest: InvalidParameterValue: Cannot terminate environment named tf-test-name-311080929528815735. It is currently pending creation.
            status code: 400, request id: 97ccb1b9-19c7-11e7-88cf-1b6eb6271a09
        

[stack72]

These break my heart but LGTM

[ghost]

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.