[rds] Add waiter for cluster actions
See original GitHub issueWaiters are only implemented for single instance RDS actions, not actions that target Aurora clusters. Can you pleased add them for the following equivalent cluster actions?
db_cluster_available
db_cluster_deleted
db_cluster_snapshot_available
db_cluster_snapshot_completed
db_cluster_snapshot_deleted
Of these we most care about the snapshots, but it would be nice to have all of them implemented.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:9
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Multi-AZ DB cluster deployments - AWS Documentation
With a Multi-AZ DB cluster, Amazon RDS replicates data from the writer DB instance to both of the reader DB instances using the...
Read more >RDS — Boto3 Docs 1.26.33 documentation - AWS
Amazon RDS gives you access to the capabilities of a MySQL, MariaDB, PostgreSQL, Microsoft SQL Server, Oracle, or Amazon Aurora database server.
Read more >How to use boto3 waiters to take snapshot from big RDS ...
Waiters have configuration parameters'delay' and 'max_attempts' like this : waiter = rds_client.get_waiter('db_instance_available') print( ...
Read more >AWS restore_db_cluster_from_snapshot yet no instances
This action only restores the DB cluster, not the DB instances for that DB ... Now, you might have to add a waiter...
Read more >Create a PostgreSQL DB Instance on AWS Relational ...
Tableau Server on Windows Help · Requirements and Recommendations · Create a PostgreSQL DB instance on Amazon RDS · Step 1: Create a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
+1 ! In our case we need
db_cluster_available
I had to implement my own waiter to solve this (example for 200 attempts with 30 seconds timeout):
and then call it when necessary
wait_until_db_cluster_ready('my_cluster')