This code fragment fails:
Where _aws_session is a boto3.session.Session() instance:
rds_client = _aws_session.client('rds')
rds_client.modify_db_instance(DBInstanceIdentifier=rds_id, ApplyImmediately=True, NewDBInstanceIdentifier='{0}-temp'.format(rds_id))
rds_waiter = rds_client.get_waiter('db_instance_available')
rds_waiter.wait(DBInstanceIdentifier='{0}-temp'.format(rds_id)) OR
rds_waiter.wait(DBInstanceIdentifier=rds_id)
print("RDS Renamed!")
What happens is if I use the old RDS identifier or the new renamed one, the waiter assumes available even though the RDS is renaming/rebooting state. Is this a bug?
This code fragment fails:
Where _aws_session is a boto3.session.Session() instance:
rds_client = _aws_session.client('rds')
rds_client.modify_db_instance(DBInstanceIdentifier=rds_id, ApplyImmediately=True, NewDBInstanceIdentifier='{0}-temp'.format(rds_id))
rds_waiter = rds_client.get_waiter('db_instance_available')
rds_waiter.wait(DBInstanceIdentifier='{0}-temp'.format(rds_id)) OR
rds_waiter.wait(DBInstanceIdentifier=rds_id)
print("RDS Renamed!")
What happens is if I use the old RDS identifier or the new renamed one, the waiter assumes available even though the RDS is renaming/rebooting state. Is this a bug?