Option to deploy the databases with pinned version.
Atlas by default picks the latest patch when we create the databases for any major version. It would be helpful if the customers can choose and control the minor version of the databases(including patch version) when we deploy the cluster. For example: We want to deploy the databases with 4.2.19 but the Atlas is automatically creating 4.2.22
This will help us identify any application dependencies on any particular patch version during our migration to Atlas, also this will help us test the patch versions in dev/lower environments before we promote the version to production.
This feature is important for us to identify any application dependencies and avoid any hiccups in production.
Application teams can have better control in terms of testing new /old features and drivers