The CDK changed the EC2 Volume to retain by default, and added a retention policy property to the EC2 Volume construct about four months ago. The RFDK's MongoDbInstance creates an EC2 Volume, but does not expose a way for the retention policy for the Volume to be set.
As a result, MongoDbInstances created by the RFDK will leave behind a data volume when destroyed.
Use Case
Cleanup after automated testing.
Proposed Solution
Just expose the removalPolicy property in the MongoDbInstanceNewVolumeProps.
This is a 🚀 Feature Request
The CDK changed the EC2 Volume to retain by default, and added a retention policy property to the EC2 Volume construct about four months ago. The RFDK's MongoDbInstance creates an EC2 Volume, but does not expose a way for the retention policy for the Volume to be set.
As a result, MongoDbInstances created by the RFDK will leave behind a data volume when destroyed.
Use Case
Cleanup after automated testing.
Proposed Solution
Just expose the removalPolicy property in the MongoDbInstanceNewVolumeProps.
This is a 🚀 Feature Request