Support migration of existing projects, clusters, ... to be CloudFormation managed
When MongoDB::Atlas::* resources are created and the specifed project, cluster, ... already exists, then these resources should not raise an error on resource creation but use the existing project, cluster, ... and apply the given configuration. In other words, the Create event that is initially sent by CloudFormation should be handled similar to an Update event but return the physical id of already existing resources. Apparently, this behaviour should be enabled by an opt-in flag.
-
AdminZuhair (Admin, MongoDB) commented
hi Stefan, this is a feature of how AWS CloudFormation itself works and less so MongoDB Atlas extensions. believe you are asking that if the resource already exists it should not return error, but update the resource and continue which seems reasonable. suggest you share this feedback with AWS CloudFormation team and we can as well at next sync. hope this helps!