Expose Volume retention policy on MongoDbInstance construct

[ddneilson]

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.

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request