Doppler sync doesn't work after upgrade to 1.30

Questions and Answers
1

We are using the Doppler Integration Service to sync secrets to Qovery. The staging and dev environments are running on the non-prod Qovery cluster, while production runs on the prod Qovery cluster.

Yesterday, we discovered that the sync for the dev and staging environments is broken. We tried resolving the issue by deleting all environment variables in Qovery and recreating the integration, but the problem persists. Interestingly, the production sync is still working. I suspect this issue might be related to the Kubernetes upgrade to version 1.30.

this is the link of service with the issue, please help to investigate and fix this sync issue, Thanks!
https://console.qovery.com/organization/b4271b12-477a-4b41-a274-9c9cba8043e8/project/f15b8795-c16f-4e96-b97e-5347595b4e19/environment/5bcd9aa4-853a-4e9a-8e6c-81e5bdd1a25e/application/2de8994d-29da-478e-8d08-3f29cac5adb4/general

2

Hi @Ethan_Huang , we will invest and sync up with the Doppler integration team. We’ll keep you posted.

3

Hi @Ethan_Huang , just to let you know that we are investigating with the Doppler team

4

I just re-enable the sync and it backs to work, Thanks!

5

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