Connect Releases

Changes:

Changes:

• [API] Added sandbox as a new type in the Deployment configuration.

Update your existing Connectors to allow automatic generation and for improved efficiency and security.

Changes:

• [API] Added inheritAs.apiClient.scopes property to connect.yaml for automated API client generation.

You can now share configuration values across all your Connect applications. This helps ensure consistency, reduce redundancy, and simplify your configuration management.

By using this template, you can reduce your implementation time while also ensuring you follow best practices for integrating with third-party services.

With the Connect CLI, you can:

• Log in to and authenticate with commercetools.
• Update and manage ConnectorStaged.
• Bootstrap a new Connector from a starter template or from one of our application templates.
• Validate Connectors locally.
• Package your code and test the dependencies locally to ensure they are loading correctly.
• Locally test the application's build and debug any incorrect dependencies.
• Run a local instance of the application in a local container.
• Validate local tests that are included in the application.
• Automatically install dependencies during project initialization.

You can now create and use common modules to share code between multiple Connect applications within a single Connector. This helps improve code efficiency, reduce implementation and maintenance time, and decrease potential bugs and inconsistencies.

By using these templates, you can reduce your implementation time while also ensuring you follow best practices for integrating with third-party services. We've introduced templates for the following use cases:

• Payment integration
• Product export
• Tax integration
• Transactional emails

• [API] Added deploymentType query parameter to Query Deployments endpoint.

You can now create and deploy assets applications using commercetools Connect. Assets applications allow you to host static content with CDN capabilities.

Changes:

• [API] Added assets to the applicationType field on ConnectorConfigurationApplication.

Changes:

• [API] Made version optional on ConnectorReference.

Changes:

• [API] Added integrationTypes field to ConnectorStagedDraft.
• [API] Added integrationTypes field to ConnectorStaged.
• [API] Added integrationTypes field to Connector.
• [API] Added Set Integration Types update action to the Connectors Staged API.
• [API] Added query parameter integrationTypes to the Query ConnectorStaged endpoint.
• [API] Added query parameter integrationTypes to the Search Connectors endpoint.
• [API] Added query parameter integrationTypes to the Query Deployments endpoint.

Changes:

• [API] Added required to StandardConfigurationKey on ConnectorStaged.
• [API] Added default to StandardConfigurationKey on ConnectorStaged.
• [API] Added required to SecuredConfigurationKey on ConnectorStaged.

Changes:

• [API] Added mc-app to the applicationType field on ConnectorConfigurationApplication.

• Connector
• Connector Staged
• Deployments

commercetools Connect lets you:

• Create private integrations for use in your own Composable Commerce Projects, or public integrations that other Composable Commerce customers can deploy.
• Deploy publicly available integrations that have been certified to ensure functionality, security, and compatibility with Composable Commerce.
• Deploy integrations without needing to provision infrastructure and runtime environments.
• Manage all aspects of commercetools Connect, from configuration to certification and deployment, using the Connect API.

The following improvements are now available for publishing and deployment of Connectors:

• When creating a production-ready or previewable Connector, you can now view errors and warnings about the release process using the publishingReport and previewableReport fields on ConnectorStaged.
• Errors and warnings are now available during the Deployment build process. This provides you with feedback regarding Connector development and highlights any issues that arise during deployment.
• You can now include a link to documentation and support channels within your Connector. By adding these links you can assist clients when they are deploying your Connector.
• You can now publish a private or public Connector to production with the Publish update action. This action replaces the Trigger Certification Process update action and allows that private connectors do not need certification. This improves flexibility for in-house Connector development and deployment.
• You can now deploy Connectors partially. This lets clients choose which Connect applications within a Connector they want to deploy.

Changes:

• [API] Added ConnectorReport to Connectors Staged.
• [API] Added documentationUrl field to ConnectorStagedDraft.
• [API] Added documentationUrl field to ConnectorStaged.
• [API] Added documentationUrl field to Connector.
• [API] Added Set Documentation URL update action to the Connectors Staged API.
• [API] Added supportUrl field to Creator.
• [API] Added logoUrl field to Creator.
• [API] Added Set Support URL update action to the Connectors Staged API.
• [API] Added Set Creator Logo update action to the Connectors Staged API.
• [API] Added noOfContributors field to Creator.
• [API] Removed noOfDevelopers field from Creator.
• [API] Added Set Number of Contributors update action to the Connectors Staged API.
• [API] Removed Set Number of Developers update action from the Connectors Staged API.
• [API] Added Publish Connector update action to the Connectors Staged API.
• [API] Removed Trigger Certification Process update action from the Connectors Staged API.
• [API] Added DeploymentReport to DeploymentDetailsBuild on Deployment.
• [API] Added the DeploymentApplicationDoNotBelong error code.
• [API] Added the DeploymentApplicationRequired error code.

You can develop your own Connect applications, or take advantage of pre-built, certified integrations that simplify processes, reduce operational costs, and minimize implementation time by launching and installing the integration.

Connect provides the following features:

• You can create Connect applications, and they can be restricted to defined Projects or made universally available to all Projects.
• Connect applications are certified to ensure functionality, security, and compatibility with commercetools Composable Commerce.
• Connect provisions the infrastructure and runtime environment for running integrations. You do not need to maintain dedicated cloud infrastructure for hosting integrations.
• From configuration to certification and deployment, all aspects of Connect are managed through the Connect API.

To learn more about Connect, check the following links:

• Overview of Connect
• Getting started
• Develop a Connect application
• Contact the Connect support team