Closed TylerSustare closed 1 year ago
Based on the POST
attempt it looks like I need to create a realm
app. But based on creating an event trigger in the console, that doesn't seem like it would be needed to create a trigger in terraform.
Thanks @TylerSustare. To learn more about what is and how to pull app_id
see here: https://www.mongodb.com/docs/atlas/app-services/admin/api/v3/#section/Project-and-Application-IDs
Also you are right, we can make this more clear in our docs. Will add this supporting link to help future users. Appreciate the feedback here.
Doc update in internal tracking INTMDB-517. Should go out as part of near term release.
Thank you @Zuhairahmed 😄 I appreciate the link to how to get the app_id
via the Atlas App Services API. And that was incredibly quick!
My real question, and what I would hope to get out of the docs though is: what mongodb resource would have this app_id
in order to not have to go outside of terraform to use the Atlas App Services API to get the app_id
?
For example, I would assume that based on the "Atlas App Services API" getting the app ID from the group/cluster ID then I could use the cluster_id
from mongodbatlas_advanced_cluster
When I try to update the TF file like this I still get the same error, just with the cluster ID.
resource "mongodbatlas_event_trigger" "otter" {
project_id = mongodbatlas_project.otter_atlas.id
app_id = mongodbatlas_advanced_cluster.otter_free.cluster_id
@TylerSustare thanks for highlighting error, this is going to require a code change. Will include as part of INTMDB-517 and let you know when issue has been resolved. Feel free to reach out if you need anything else in the interim.
This issue has gone 30 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!
bump
Hi, is there any update on this please? We're facing a similar problem.
hi @Ballymultani @TylerSustare we should have an update on this soon. feel free to reach out if you need anything else in the interim.
Hi, any update?
Is there any plan to add App Services resource types?
@TylerSustare @Ballymultani fix for this has been picked up for v1.8.1 sprint which should be released in ~3 weeks. @Futhark yes we are planning to integrate Atlas App Services into Atlas Admin API/Terraform Provider, but this is a large effort and still several quarters away. Feel free to reach out in future and can share updates if you need.
@TylerSustare @Ballymultani @Futhark v1.8.1 has been published to the Terraform Public Registry! take a spin and let us know if you need anything else.
closing this issue, but feel free to re-open if you need anything else here
Hi,
Since the 1.8.1 release how to get app_id (without leaving terraform or adding static values) please? Neither mongodbatlas_advanced_cluster.otter_free.cluster_id or mongodbatlas_advanced_cluster.otter_free.id works
tl;dr;
The
app_id
to create an Atlas Event Trigger in the documentation is ambiguous. What is your application in the doc talking about here?Terraform CLI and Terraform MongoDB Atlas Provider Version
Terraform Configuration File
Steps to Reproduce
$ terraform apply -auto-approve
Expected Behavior
app
should be relating to theapp_id
Actual Behavior
Debug Output
Additional Context
Not needed.
References
According to the doc for event triggers we need the
app_id
but the example shows a string as an example. In theArgument Reference
section it doesn't help to know what the Application should be.