The documentation you are viewing is for Dapr v1.9 which is an older version of Dapr. For up-to-date documentation, see the latest version.
commercetools GraphQL binding spec
Detailed documentation on the commercetools GraphQL binding component
To setup commercetools GraphQL binding create a component of type
bindings.commercetools. See this guide on how to create and apply a binding configuration.
apiVersion: dapr.io/v1alpha1 kind: Component metadata: name: <NAME> spec: type: bindings.commercetools version: v1 metadata: - name: region # required. value: region - name: provider # required. value: provider (gcp/aws) - name: projectKey # required. value: project-key - name: clientID # required. value: ***************** - name: clientSecret # required. value: ***************** - name: scopes # required. value: scopes
WarningThe above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described here.
Spec metadata fields
|region||Y||Output||The region of the commercetools project||
|provider||Y||Output||The cloud provider, either gcp or aws||
|projectKey||Y||Output||The commercetools project key||
|clientID||Y||Output||The commercetools client ID for the project||
|clientSecret||Y||Output||The commercetools client secret for the project||
|scopes||Y||Output||The commercetools scopes for the project||
For more information see commercetools - Creating an API Client and commercetools - Regions.
This component supports output binding with the following operations:
- Basic schema for a Dapr component
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
- Sample app that leverages the commercetools binding with sample GraphQL query
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
Last modified January 3, 2023: fix link (3ce9862a)