elastic_beanstalk_environment wait_for_ready_timeout documentation wrong

[archgrove]

Version

0.9.3

Affected Resource(s)

AWS elastic_beanstalk_environment

Description

Commit cd79471 (for PR #13359) altered the default wait_for_ready_timeout on EB instances from 10 to 20 minutes, but did not update the documentation to reflect this.

I've two solutions:

1. A trivial PR at that corrects the documentation: Make wait_for_ready_timeout default match code #14149
2. Revert cd79471ecbad41b8bb9e70cc5e8e47b210cc3f32: As it stands, it'll cause everyone using the default timeout to have an unexpected change in their next plan. The change was done in reference to provider/aws: Increase Beanstalk env 'ready' timeout #13359, and fixes a test failure to due (I assume) overrunning EB waits, but seems like a blunt instrument. I've not looked in detail, so it might well be the most sensible thing to do, but the knock-on effect to end users is a bit sad. However, it might be too late, as this went out in 0.9.3?

[radeksimko]

Fixed via #14149

I'll make sure to think about graceful migration paths next time.
Sorry if it caused any inconvenience.

[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.