Hi @Leonardo_Bispo can you share more details so we can best advise? In particular, can you include link to GitHub repo in question, your deployment details including Terraform/3rd party integration scripts, and full error message/logs if available?
Failed: error validating ‘mongodb-atlas’ service: expected ‘uri’ to be a ‘string’, but instead found a ‘null’
@Zuhair_Ahmed it is using the " App Services GitHub Integration " rather than a custom terraform/3rd party script.
It seems like if i commit anything from the UI it updates GitHub correctly however anything which is committed into GitHub is then rejected by Atlas. (even something as trivial as a comment in a function)
I started experiencing the same thing on 3/26. No change in the configurations. I exported the last successful deploy and the one failing, and diff them, and see no difference. I also make the change in the UI and push to Github, and it is successful. The exported deployment and the pushes from Atlas UI to github repo all are identical to the failed deployment (just changing a Readme file to trigger a deploy/Github webhook). Something appears to have changed with the integration.
We solved this by upgrading to their new CLI package “atlas-app-services-cli”. The only special thing I needed to do was ensure the cluster was set in the data_sources/mongodb-atlas/config.json file (“config”: { “clusterName”: … } and it seems functions and triggers must also have identical names now.