Push failed: cannot have duplicate service name

MongoDB Atlas App Services & Realm
1

Could the recent release on March 3rd, where the Service Name for a datasource now defaults to the Cluster Name in the CLI and the prompt to choose a Service Name has been removed,
be causing issues with CLI push failures when modifying functions or triggers that rely on existing datasources with custom names?

2

Hi Support, I’m having the same issue. We are updating the production instance and this is stalling our updates.

3

Hi @Sajithlal_k and @Leninkumar_Perumalsamy,

This is a known issue, due to the change in configuration format: the procedure to solve it is as follows (with the appservices tool)

  • Ensure you’re logged in to the app affected
  • Pull the app configuration to a fresh directory (i.e. not the existing local configuration)
  • From the configuration folder, remove the contents of the services folder
  • Push the configuration: this should go through without errors
  • Once again, pull the configuration to a fresh directory: this should now have the new configuration format, and you can start working on it for the future releases.

Hope that helps!

4

Hi Paolo,

Removing the services folder from the configuration helped. thank you.

Regards,
LKP.

5

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.