provider/aws: Report available sooner for RDS #2014
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements option number 2 from #1097.
In order to speed up our creation time, but still not progress until we can safely do so, we report an
available
status for the database if we're waiting on a backup, and our status isbacking-up
. This state is reached once the database is up and running, but AWS won't reportavailable
until the backup is done.The output for a database with no backups:
And with a
backup_retention_period
> 1:... and then we go about our business.
The decimation on instance backups (here) mentions some I/O caveats:
It's probably acceptable in our case.
cc @radeksimko and @phinze for thoughts
We also add extra
[DEBUG]
here so people can see the status of the operation, e.g.creating
,backing-up
etc