Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RDS Aurora start/stop_db_cluster
See original GitHub issueHi,
Currently trying to use AWS Instance Scheduler to ‘start/stop_db_cluster’. I noticed in the code within the ‘rds_service.py’ file the following is written:
if rds_inst["Engine"] in ["aurora"]: self._logger.debug(DEBUG_UNSUPPORTED_ENGINE, rds_inst["Engine"], db_id) return False
If my understanding is correct. This will flag aurora as the DB Engine and skip it.
My question is: Will AWS Instance Scheduler support the use of ‘start/stop_db_cluster’ as it currently only supports ‘start/stop_db_instance()’
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:19 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We will support RDS Aurora, Multi-AZ instances and EC2 Hibernation in our next maintenance release that is under test. I can provide you with link to preview if you’re interested in testing it.
Fixed in v1.2.0