As a database administrator or developer,
I would like to perform a cascade power off operation on a database service with read replicas when a power off operation is initiated,
so that the service hierarchy is navigated, starting with powering off the replicas and ending with the master, all in a single uninterrupted transaction.
This feature aims to prevent customers from having to set up automatic schedulers on their environments, reducing resource waste and ensuring a seamless and efficient power off process for the database service.