Terraform Provider
It would be nice to be able to managed Realm Applications via Terraform, similar to how MongoDB Atlas can currently be managed via the mongodb_atlas from Terraform provider.
Gene
shared this idea
-
AdminZuhair
(Admin, MongoDB)
commented
Thanks for sharing feedback Gene, Jacob, and Andrew. We are planning on exposing a greater number of Atlas App Services resources in the Terraform MongoDB Atlas Provider in future, but this effort is still several quarters away. In the interim you can leverage the Atlas App Service API or Atlas UI. Hope this helps. See here for more details: https://www.mongodb.com/docs/atlas/app-services/manage-apps/create/create-with-api/
-
Jacob
commented
The mongodbatlas terraform provider allows the creation of triggers but they require an app id and "config service id". The app id refers to the id of an app services application and the config service id is a linked data source. You cannot create an app services app or linked data source using the terraform provider and therefore you cannot create triggers with the provider alone. The provider should be updated to allow the creation of the app_id and config_service_id objects.
-
Andrew
commented
I agree. Example: Triggers. Triggers can be created with the Atlas Terraform Provider but take inputs from the Realm side in app_id and config_service_id. Per MongoDB Support, these would require a Realm Provider and until then must be manually gathered and input into the Trigger resource, making for a clunky user experience.