Merge pull request #3052 from spryker/alumio

remove alumio
spryker · Feb 24, 2025 · 33d3029 · 33d3029
2 parents 3632d8e + b36b9f4
commit 33d3029
Show file tree

Hide file tree

Showing 43 changed files with 60 additions and 1,700 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -49,7 +49,7 @@ jobs:
 
       - name: Cache HTMLProofer
         id: cache-htmlproofer
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: tmp/.htmlproofer
           key: ${{ runner.os }}-check_about_all-htmlproofer
@@ -77,7 +77,7 @@ jobs:
 
       - name: Cache HTMLProofer
         id: cache-htmlproofer
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: tmp/.htmlproofer
           key: ${{ runner.os }}-check_cloud-htmlproofer
@@ -105,7 +105,7 @@ jobs:
 
       - name: Cache HTMLProofer
         id: cache-htmlproofer
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: tmp/.htmlproofer
           key: $-check_pbc-htmlproofer
@@ -133,7 +133,7 @@ jobs:
 
       - name: Cache HTMLProofer
         id: cache-htmlproofer
-        uses: actions/cache@v2
+        uses: actions/cache@v4
         with:
           path: tmp/.htmlproofer
           key: ${{ runner.os }}-check_sdk-htmlproofer

diff --git a/Rakefile b/Rakefile
@@ -103,7 +103,8 @@ commonOptions = {
     /www.mysql.com\/[\.\w\-\/\?]+/,
     /www.gnu.org\/[\.\w\-\/\?]+/,
     /algolia.com\/[\.\w\-\/\?]+/,
-    /mysql.com\/[\.\w\-\/\?]+/,    
+    /www.cursor.com\/[\.\w\-\/\?]+/,
+    /www.mysql.com\/[\.\w\-\/\?]+/,
     /wt.io\/[\.\w\-\/\?]+/,
     /www.facebook.com\/[\.\w\-\/\?]+/
 

diff --git a/_data/sidebars/pbc_all_sidebar.yml b/_data/sidebars/pbc_all_sidebar.yml
@@ -1089,31 +1089,6 @@ entries:
             url: /docs/pbc/all/data-exchange/create-post-plugins-for-data-exchange-api.html
             include_versions:
             - "202410.0"
-          - title: Spryker Middleware powered by Alumio
-            url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/spryker-middleware-powered-by-alumio.html
-            nested:
-              - title: Integration apps
-                url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/integration-apps.html
-              - title: Incrementally import recently updated products
-                url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/incrementally-import-products-with-spryker-middleware-powered-by-alumio.html
-                include_versions:
-                - "202404.0"
-                - "202410.0"
-                nested:
-                - title: Akeneo PIM Integration App
-                  url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.html
-                  nested:
-                    - title: Configure the Akeneo PIM Integration App
-                      url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app.html
-                      nested:
-                      - title: Configure the Spryker Middleware powered by Alumio connection with Akeneo PIM and SCCOS
-                        url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-smpa-connection-with-akeneo-pim-and-sccos.html
-                      - title: Configure data mapping between Akeneo and SCCOS
-                        url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.html
-                      - title: Configure the data integration path between Akeneo and SCCOS
-                        url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html
-                      - title: Create tasks and import products from Akeneo to SCCOS
-                        url: /docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/create-tasks-and-import-products-from-akeneo-to-sccos.html
 
           - title: Data Exchange FAQ
             url: /docs/pbc/all/data-exchange/data-exchange-faq.html

diff --git a/...h-spryker-middleware-powered-by-alumio.md → ...h-spryker-middleware-powered-by-alumio.md b/...h-spryker-middleware-powered-by-alumio.md → ...h-spryker-middleware-powered-by-alumio.md
@@ -3,6 +3,8 @@ title: Incrementally import recently updated products with Spryker Middleware Po
 description: Learn how to incrementally import products that have been updated a day ago
 last_updated: Apr 18, 2024
 template: howto-guide-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/incrementally-import-products-with-spryker-middleware-powered-by-alumio.html
 ---
 
 This document describes how to import products that have recently been updated. Following the described procedure, you can import products that have been updated within the past day.

diff --git a/...gration-app/akeneo-pim-integration-app.md → ...gration-app/akeneo-pim-integration-app.md b/...gration-app/akeneo-pim-integration-app.md → ...gration-app/akeneo-pim-integration-app.md
@@ -3,6 +3,8 @@ title: Akeneo PIM Integration App
 description: Learn how you can import products from Akeneo to your Spryker projects with Akeneo PIM Integration App
 last_updated: August 7, 2023
 template: concept-topic-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/akeneo-pim-integration-app.html
 ---
 
 The Akeneo PIM Integration App lets you import products from Akeneo PIM to your Spryker project.
@@ -13,7 +15,7 @@ You can import the following product data:
 - Product hierarchy (abstract product information with its variants)
 - Digital assets (for example, product images)
 - Product categories
-- Product attributes 
+- Product attributes
 - Product super attributes
 - Product relations
 - Product labels
@@ -29,9 +31,9 @@ You can initiate the product import manually whenever you need, set up the sched
 To use the Akeneo PIM Integration App, you need to have the Spryker Middleware powered by Alumio. To obtain it, reach out to [Spryker support](https://spryker.com/support/).
 The Akeneo PIM Integration App works with B2C and B2B business models of Spryker Cloud Commerce OS (SCCOS). At the moment, it doesn't cover the Marketplace business models.
 
-## Importing product structure from Akeneo to Spryker 
+## Importing product structure from Akeneo to Spryker
 
-Akeneo lets you create products with up to 3 levels of enrichment, while Spryker lets you select multiple super attributes to enrich product information and create product variants. 
+Akeneo lets you create products with up to 3 levels of enrichment, while Spryker lets you select multiple super attributes to enrich product information and create product variants.
 
 For example, if you want to create a T-shirt with varying sizes and colors, here is how it's created in Akeneo:
 *Root* Product Model = T-shirt
@@ -40,7 +42,7 @@ For example, if you want to create a T-shirt with varying sizes and colors, here
 
 When importing this data into Spryker, the following applies:
 - Level 1 Product Models from Akeneo are imported as abstract products into Spryker. In our example, this means that two abstract products are created in SCCOS: a yellow T-shirt and a red T-shirt.
-- Level 2 variants are imported as concrete products of the abstract product. In our example, this means that two concrete products are created per each product abstract in Spryker: 
+- Level 2 variants are imported as concrete products of the abstract product. In our example, this means that two concrete products are created per each product abstract in Spryker:
 - For the yellow T-shirt abstract product, a yellow T-shirt small and a yellow T-shirt large concrete products
 - For the red T-shirt abstract product, a red T-shirt small and a red T-shirt large concrete products
 
@@ -61,5 +63,3 @@ The following table represents the high-level mapping of product data between Ak
 
 ## Next steps
 [Configure the Akeneo PIM Integration App](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app.html)
-
-
diff --git a/...-data-mapping-between-akeneo-and-sccos.md → ...-data-mapping-between-akeneo-and-sccos.md b/...-data-mapping-between-akeneo-and-sccos.md → ...-data-mapping-between-akeneo-and-sccos.md
@@ -1,7 +1,9 @@
 ---
 title: Configure data mapping between Akeneo and SCCOS
-description: Create data transformers in the Spryker Middleware powered by Alumio
+description: Learn how you can configure and map data between Akeneo and Spryker Cloud Commerce OS connecting the two together.
 template: howto-guide-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-data-mapping-between-akeneo-and-sccos.html
 last_updated: Nov 17, 2023
 ---
 

diff --git a/...nfigure-the-akeneo-pim-integration-app.md → ...nfigure-the-akeneo-pim-integration-app.md b/...nfigure-the-akeneo-pim-integration-app.md → ...nfigure-the-akeneo-pim-integration-app.md
@@ -2,6 +2,8 @@
 title: Configure the Akeneo PIM Integration App
 description: Learn how you can configure the Akeneo PIM Integration App in the Spryker Middleware powered by Alumio
 template: concept-topic-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app.html
 last_updated: Nov 10, 2023
 ---
 

diff --git a/...egration-path-between-akeneo-and-sccos.md → ...egration-path-between-akeneo-and-sccos.md b/...egration-path-between-akeneo-and-sccos.md → ...egration-path-between-akeneo-and-sccos.md
@@ -2,6 +2,8 @@
 title: Configure the data integration path between Akeneo and SCCOS
 description: Create incoming configuration, outgoing configuration, and route in the Spryker Middleware powered by Alumio
 template: howto-guide-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html
 last_updated: Nov 10, 2023
 ---
 
@@ -23,7 +25,7 @@ To create the incoming configuration, do the following:
 3. Optional: In *Description*, add the description of your incoming configuration.
 4. To activate the incoming configuration, set the status to *Enabled*.
 5. In the *Subscriber* field, select the *HTTP subscriber*. You may also select the *Akeneo subscriber*, however, in this document, we consider the settings for the *HTTP subscriber*.
-6. In the *Request URL*, specify the URL to a specific product or the URL to a list of products. The URL should include just the path after `akeneo.com`, as the base path to the Akeneo environment is already specified in the HTTP client you created. For example, if the actual path to a specific product you want to import from Akeneo is `https://test.cloud.akeneo.com/api/rest/v1/producs/1234567890`, the path to specify in the *Request URL* field is `/api/rest/v1/producs/1234567890`. 
+6. In the *Request URL*, specify the URL to a specific product or the URL to a list of products. The URL should include just the path after `akeneo.com`, as the base path to the Akeneo environment is already specified in the HTTP client you created. For example, if the actual path to a specific product you want to import from Akeneo is `https://test.cloud.akeneo.com/api/rest/v1/producs/1234567890`, the path to specify in the *Request URL* field is `/api/rest/v1/producs/1234567890`.
 
 {% info_block infoBox "Batch products import" %}
 
@@ -53,7 +55,7 @@ The incoming configuration should now appear at the *Configurations -> Incoming*
 2. In *Name*, enter the Name of your configuration. As you are entering the name, the identifier will be populated automatically based on the name.
 3. Optional: In the **Description** field, add the description of your incoming configuration.
 4. To activate the incoming configuration, set the status to *Enabled*.
-5. In the *Subscriber* field, select the subscriber. 
+5. In the *Subscriber* field, select the subscriber.
   QUESTION: What is the subscriber, what is each subscriber in the dropdown for, and how do they know which subscriber to select here?
 6. In *Entity*, select the entity depending on what data you want to import from Akeneo. For example, to import product abstracts, select *Get list of products*.
 7. Leave the *Input transformer* field empty.
@@ -92,10 +94,9 @@ To define the route, do the following:
 6. In *Outgoing configuration*, select the outgoing configuration created at step [Create and outgoing configuration](#create-an-outgoing-configuration).
 ![create-a-new-route](https://spryker.s3.eu-central-1.amazonaws.com/docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos/create-a-new-route.png)
 
-7. Click **Save & Continue**. 
+7. Click **Save & Continue**.
 
 The route should now appear on the *Configurations -> Routes* page.
 
 ## Next step
 [Create tasks and import products from Akeneo into SCCOS](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/create-tasks-and-import-products-from-akeneo-to-sccos.html)
-
diff --git a/...a-connection-with-akeneo-pim-and-sccos.md → ...a-connection-with-akeneo-pim-and-sccos.md b/...a-connection-with-akeneo-pim-and-sccos.md → ...a-connection-with-akeneo-pim-and-sccos.md
@@ -2,9 +2,11 @@
 title: Configure the Spryker Middleware Powered by Alumio connection with Akeneo PIM and SCCOS
 description: Create clients for Akeneo and Spryker in the Spryker Middleware Powered by Alumio
 template: howto-guide-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-smpa-connection-with-akeneo-pim-and-sccos.html
 last_updated: Nov 10, 2023
 ---
-To start importing products from Akeneo to your Spryker project using the Spryker Middleware powered by Alumio, you need to connect Spryker Middleware powered by Alumio with Akeneo and SCCOS. 
+To start importing products from Akeneo to your Spryker project using the Spryker Middleware powered by Alumio, you need to connect Spryker Middleware powered by Alumio with Akeneo and SCCOS.
 
 You can establish this connection directly in the Spryker Middleware Powered by Alumio platform by following these guidelines.
 
@@ -33,7 +35,7 @@ To connect Akeneo with Spryker Middleware powered by Alumio, you need to create
 6. Optional: Check the *Enable logging of requests* checkbox.
 7. Click **Grant access to Alumio** and proceed to the next step.
 8. Enter the name of your client. As you are entering the name, the identifier will be populated automatically based on the name.
-9. Click **Save**. 
+9. Click **Save**.
 
 The client should now be on the list of the *HTTP clients* page.
 
@@ -50,7 +52,7 @@ To connect SCCOS to Spryker Middleware powered by Alumio, you also need to creat
 7. Optional: Check the *Enable logging of requests* checkbox.
 8. Click **Grant access to Alumio** and proceed to the next step.
 9. Enter the name of your client. As you are entering the name, the identifier will be populated automatically based on the name.
-10. Click **Save**. 
+10. Click **Save**.
 
 The client should now be on the list of the *HTTP clients* page.
 

diff --git a/...d-import-products-from-akeneo-to-sccos.md → ...d-import-products-from-akeneo-to-sccos.md b/...d-import-products-from-akeneo-to-sccos.md → ...d-import-products-from-akeneo-to-sccos.md
@@ -2,19 +2,21 @@
 title: Create tasks and import products from Akeneo to SCCOS
 description: Test the configuration, create tasks, schedulers and run the import of products from Akeneo to SCCOS
 template: howto-guide-template
+redirect_from:
+  - /docs/pbc/all/data-exchange/202410.0/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/create-tasks-and-import-products-from-akeneo-to-sccos.html
 last_updated: Nov 10, 2023
 ---
 
 After you have [configured the data integration path between Akeneo and SCCOS](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html), you have to test the created configuration, create tasks and, optionally, schedulers for running the import.
 
 ## Create a task for the products import from Akeneo
 
-To create a task for the products import from Akeneo, you have to run the incoming created at step [Create an incoming configuration](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html#create-an-incoming-configuration). 
+To create a task for the products import from Akeneo, you have to run the incoming created at step [Create an incoming configuration](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html#create-an-incoming-configuration).
 
 To run the incoming, do the following:
 
 1. In the Spryker Middleware powered by Alumio platform, go to **Connections -> Incoming** and click the necessary incoming configuration.
-2. In the top right corner, click **Run incoming**. 
+2. In the top right corner, click **Run incoming**.
 3. Go to *Tasks* and make sure that there is the new task with the route you created at step [Define the route](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html#define-the-route). The task's status should be *Processing*.
 
 ![tasks](https://spryker.s3.eu-central-1.amazonaws.com/docs/pbc/all/data-exchange/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/create-tasks-and-import-products-from-akeneo-to-sccos/tasks.png)
@@ -27,7 +29,7 @@ A separate task is created for every product. That is, if you initiate an incomi
 
 ### Filtering task messages
 
-You can filter the task messages by different categories such as info, notice, error, and others. This is especially useful when you need to determine a reason why the task execution has failed. In such a case, you can filter the messages by errors and see details of the errors. 
+You can filter the task messages by different categories such as info, notice, error, and others. This is especially useful when you need to determine a reason why the task execution has failed. In such a case, you can filter the messages by errors and see details of the errors.
 To filter the messages, do the following:
 1. On the *Tasks* page, click the necessary task, for example, the one with the *Failed* status.
 2. On the task details page, go to *Export Messages* tab.
@@ -55,7 +57,7 @@ The product that will be imported into SCCOS, appears at the bottom of the trans
 
 ## Run the route
 
-To get the task processed, you need to run the full route. 
+To get the task processed, you need to run the full route.
 To run the route, do the following:
 1. Go to *Routes* and click the route you created at step [Define the route](/docs/pbc/all/data-exchange/{{page.version}}/spryker-middleware-powered-by-alumio/integration-apps/akeneo-pim-integration-app/configure-the-akeneo-pim-integration-app/configure-the-data-integration-path-between-akeneo-and-sccos.html#define-the-route).
 2. At the *Routes* page, click **Run route**.
@@ -84,7 +86,7 @@ To create the scheduler, do the following:
 5. In *Expression*, enter the time you want the scheduler to run. Use [Crontab guru](https://crontab.guru/) to set the time in the right format.
 6. Create one more scheduler with the same parameters, but for step 3, select the *Run outgoing configuration* job.
 
-Since the number of tasks that can be processed is limited, it's recommended to create a scheduler that would remove completed tasks after the specified intervals. 
+Since the number of tasks that can be processed is limited, it's recommended to create a scheduler that would remove completed tasks after the specified intervals.
 
 To create such a scheduler, do the following:
 
@@ -97,4 +99,4 @@ To create such a scheduler, do the following:
 
 ## Check the product in the SCCOS Back Office
 
-To check the imported product in the SCCOS Back Office, go to **Catalog -> Products** and check if the product appeared on the list.
+To check the imported product in the SCCOS Back Office, go to **Catalog -> Products** and check if the product appeared on the list.