Import resources from MongoDBcloud

[eladazary]

Hi,

I would like to use your tool only for user creation. In order to do that I need to create a project.
Can you please add support in importing resources as project/clusters so that I wouldn't need to create a new project?

Thanks,
Elad

[Knappek]

Hi @eladazary, thank you for this feature request, this is a good idea. We should think about this import functionality for all resources, i.e. projects, clusters, database-users and alert configurations. Meaning, if someone started with Atlas manually, they can easily import everything to be managed via the operator.

This feature could be more tricky than expected: How do we implement this? we have multiple options:

1. you create a resource on the K8s cluster (e.g. a a project like this). A problem is when the spec differs from the already existing setup. The operator will override the existing setup with the one provided in the spec. Is this fine?
2. create a resource with an empty spec which tells the operator that the resource already exists and let the operator fill in the spec with all configurations. Question is: is it cool to have the operator modify the spec? It should only touch the status, but not the spec, the spec is for users to modify/tell the operator about changes.

What's you opinion on that?

[eladazary]

Hi Andreas, Thanks for the reply, I think that nobody should touch the spec but the user and the operator should stick to a specific state (As in terraform). Or, the operator will use the API Key we insert and send API commands to MongoDB Atlas for fetching the current resources. Both ways sounds awesome ! Looking forward for this feature. Thanks, ‫בתאריך יום א׳, 29 בדצמ׳ 2019 ב-15:53 מאת ‪Andreas (Andy) Knapp‬‏ <‪ [email protected]‬‏>:‬

…

Hi @eladazary <https://github.com/eladazary>, thank you for this feature request, this is a good idea. We should think about this import functionality for all resources, i.e. projects, clusters, database-users and alert configurations. Meaning, if someone started with Atlas manually, they can easily import everything to be managed via the operator. This feature could be more tricky than expected: How do we implement this? we have multiple options: 1. you create a resource on the K8s cluster (e.g. a a project like this <https://github.com/Knappek/mongodbatlas-operator/blob/master/deploy/crds/knappek_v1alpha1_mongodbatlasproject_cr.yaml>. A problem is when the spec differs from the already existing setup. The operator will override the existing setup with the one provided in the spec. Is this fine? 2. create a resource with an empty spec which tells the operator that the resource already exists and let the operator fill in the spec with all configurations. Question is: is it cool to have the operator modify the spec? It should only touch the status, but not the spec, the spec is for users to modify/tell the operator about changes. What's you opinion on that? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27?email_source=notifications&email_token=AJAVJPN6E4JPTOJZDPNFIMLQ3CTXJA5CNFSM4KAZ6CM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHY77PY#issuecomment-569507775>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJAVJPKX2GVK74WZBF5FR63Q3CTXJANCNFSM4KAZ6CMQ> .

[Knappek]

I will think about how to implement it...if you want to go ahead and start implementing, feel free to do it. We could split this feature in several PRs for all separate resources and start with the simplest one, a project.

[eladazary]

I will try to find some time to work on it.
Do you know if there is a way to create the DB users without creating a cluster via the operator?
I would like to create a user but it keeps telling me that "MongoDBAtlasProject.knappek.com "" not found"

[Knappek]

You mean "..without creating a project via the operator...", right?
Unfortunately, this is not possible, as it is trying to get the project information from the MongoDBAtlasProject CRD: https://github.com/Knappek/mongodbatlas-operator/blob/master/pkg/controller/mongodbatlasdatabaseuser/mongodbatlasdatabaseuser_controller.go#L101-L110

I think we should definitely add the import functionality to be able to start managing existing resources with the operator.
In theory, this functionality should be available already for projects as you can see in these lines where the status will be filled if the operator finds an existing porject.