This tool automates restoration of RDS database instances from snapshots into any dev, staging or production environments. It supports individual RDS Snapshot as well as cluster snapshot restore operations.
Currently Trapheus supports a limited set of input parameters to the state machine as defined here: https://github.com/intuit/Trapheus#-execution. Theidentifier parameter refers to the rds instance/cluster id.
The state machine works on the assumption/prerequisite that the restoration will be done using a snapshot with identifier in the format <identifier-snapshot> or snapshot creation will create/update snapshot with identifier as <identifier-snapshot>.
As part of this issue, we would like to add an enhancement where users can provide a unique snapshot-identifier as an additional input parameter to the state machine and the snapshot id provided as a value for this parameter be used for the db restoration process (when task=db_restore)
This pull request has been automatically closed because it has been inactive for more than 14 days. Please reopen if you still intend to submit this pull request.
Currently Trapheus supports a limited set of input parameters to the state machine as defined here: https://github.com/intuit/Trapheus#-execution. The
identifier
parameter refers to the rds instance/cluster id.The state machine works on the assumption/prerequisite that the restoration will be done using a snapshot with identifier in the format <
identifier
-snapshot> or snapshot creation will create/update snapshot with identifier as <identifier
-snapshot>.As part of this issue, we would like to add an enhancement where users can provide a unique
snapshot-identifier
as an additional input parameter to the state machine and the snapshot id provided as a value for this parameter be used for the db restoration process (whentask
=db_restore)Refer https://github.com/intuit/Trapheus#-execution for more details on
task
types