What problem are you trying to solve?

Focus on the what and why of the need you have, not the how you'd like it solved.

We need to be able to provision our Mongo Atlas cluster fully in IaC using AWS CDK (typescript), without relying on click-ops.

This includes setting up the "Triggers" App Service so that we are able to use the (existing & working) CfnTrigger construct afterwards (as provided by the awscdk-resources-mongodbatlas package).

What would you like to see happen?

Describe the desired outcome or enhancement.

There is a construct in the awscdk-resources-mongodbatlas package that allows us to bootstrap/setup the "Triggers" App Service of a given Mongo Atlas project and an existing data source (to link it to).

Link to related GitHub Issue: https://github.com/mongodb/awscdk-resources-mongodbatlas/issues/517

Why is this important to you or your team?

Explain how the request adds value or solves a business need.

We use AWS CDK exclusively for our IaC.

This works well for a lot of Mongo Atlas Resources (Clusters, Database Users, Private Link etc.).

However to use triggers (and the existing CfnTrigger construct), the "Triggers" App Service needs to be enabled for a Mongo Atlas Project.

This at the moment, cannot be done through AWS CDK, forcing us to use click-ops, which is bad.

What steps, if any, are you taking today to manage this problem?

We're forced to use click-ops to set up the "Triggers" App Service in the Mongo Atlas Web UI.