Skip to main content

Are you using commercetools connect apps that are published by 3rd parties? Definitely awesome set of connects available for use to connect with your regular integrations - Klaviyo, Stripe, etc., I find them very good but I also see that in the recent times there are issues trying to deploy them as they are not kept uptodate (commercetools seem to have changed something on their end in the Publishing process) probably because of different priorities from the Integrators who have published this? Shouldnt commercetools validate them once in a while and mark them as stale or inform the integrators so they can publish an updated version of their connect apps? We have been really struggling to get the above working. The publication fails with minimal error info and its difficult to understand what went wrong - the commercetools cli with connect validate option doesnt work in Windows and inconsistent in Mac - with little or no documentation. 

Any one else using these or other connect apps and having similar issues ? Any help would really be appreciated. 

Hi @Naga, 
Thanks so much for your feedback we really appreciate your interest in Connect and I hope I can give some answers to the questions you bring.
Regarding some integrations having issues being deployed, we see that some of these connectors have had issues when deploying due to security issues, we take security very seriously and even Connectors that could have been certified as recently as yesterday are susceptible of containing a dependent library where some vulnerability is detected. We chose to prioritize quality and security over speed and convenience, that is why you can find connectors being stopped.
As you mention the information we give is not enough, and this has been feedback also from other customers, this is why the team is literally working on improving the observability of the product as I write this post, we prioritized such improvement to address the need for it and we hope to deliver within this quarter.
Of course the next logical step many take is to fork the connector and solve those dependencies that could be blocking the deployment themselves, leveraging on the openness of Connect and the possibility of creating private connectors, for this definitely the CLI is the way to go, has Documentation fresh from the oven, but being a newly released product I would like to know more on those inconsistencies you mention (specially on Mac)

Reply


Terms & ConditionsCookie settings