Skip to Main Content

MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Status Submitted
Categories Atlas
Created by Guest
Created on Jun 29, 2023

Uniform approach to Dedicated and Tenant clusters in terraform mongodbatlas_advanced_cluster

Our software development lifecycle has 5 environments. We also wish to spin up dedicated, short lived environments for individual Developers. As a result, we'd like to have two M40s, an M10 and two M5s for our SDLC and the ability to spin up M0s for the devs. The way you've implemented the terraform mongodb_advanced_cluster resource makes it exceptionally difficult to use the same code across all environments. This isn't in keeping with best practice for terraform implementations, which is to use the same code and only change the variables. Might I suggest you add provider_type and allow values such as "DEDICATED" and "TENANT" and change provider_name to be used for both tenant and dedicated. This would allow you to get rid of backing_provider_name. Also, make variable declaration uniform across all provider_type installations.
  • Attach files