Skip to content

Update store-configuration.md - add composer instance import/export #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update store-configuration.md - add composer instance import/export #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/composer/integration-hub/store-management/store-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,9 @@ The following Commerce objects are included when importing/exporting store confi
- [Catalogs](/docs/api/pxm/catalog/create-catalog)
- [Catalog Rules](/docs/api/pxm/catalog/rules)
- [Payment Gateway](/docs/api/payments/gateways). The following fields are masked when exporting payment gateways: **password**, **username**, **login**, **merchant_account**, **signature**, **stripe_account**, **merchant_id**, **private_key**, **public_key**, **payer_id**. These fields must be replaced by real values before importing the configuration.
- [Composer Integration Instances](https://elasticpath.dev/docs/composer/). During export, both enabled and disabled instegration instances are retrieved and marked with the flag `enabled` equals to true or false. During import `enabled` flag is ignored and all integration instances are imported. If the configuration includes an integration that has not been published in the Integrations Hub, the process of importing the integration instance will fail. Ensure that all integrations are published in the Integrations Hub before importing the configuration. All the fields containing "key" or "secret" in the name are masked during exporting integration instances. Before importing configuration those fields need to be replaced with real values. During export, both enabled and disabled instegration instances are retrieved and marked with the flag `enabled` equals to true or false. During import `enabled` flag is ignored and all integration instances are imported.


A Store Configuration Orchestrator Delete Action deletes [products](/docs/api/pxm/products/products) from a store.

For more information, watch a video.
Expand Down Expand Up @@ -70,7 +72,8 @@ Once you have [installed Store Configuration Orchestrator](#installing-store-con
- **Token URL** - Your Commerce API Token URL. For example, `https://euwest.cm.elasticpath.com/oauth/<access_token>` (EU) or `https://useast.api.elasticpath.com/oauth/<access_token>` (US).

1. Click **Connect** to make sure that the authentication is completed successfully.
1. Click **Next**. The **Store Orchestrator Configuration** page is displayed. The table below describes the options you can configure, depending on the Store Configuration Orchestrator action you are performing.
1. Enter **Integrations Hub API Domain** (us-east-2.elasticpathintegrations.com or eu-west-1.elasticpathintegrations.com)
2. Click **Next**. The **Store Orchestrator Configuration** page is displayed. The table below describes the options you can configure, depending on the Store Configuration Orchestrator action you are performing.

| Option | Action | Description |
|:--- |:--- | :--- |
Expand Down