Merge branch 'main' into CEXT-3900

Author: keharper

package.json

@@ -6,7 +6,7 @@
     "url": "https://github.com/AdobeDocs/commerce-extensibility"
   },
   "dependencies": {
-    "@adobe/gatsby-theme-aio": "4.14.16",
+    "@adobe/gatsby-theme-aio": "4.14.17",
     "gatsby": "4.22.0",
     "react": "^17.0.2",
     "react-dom": "^17.0.2"

src/pages/admin-ui-sdk/publish.md

@@ -26,7 +26,13 @@ During the testing phase, an administrator of your enterprise organization perfo
 
 ## Update an already published application
 
-To update an already published application, you must revoke it and go through the approval process again.
+To deploy code changes to an already published application, you can perform a force deploy:
+
+```bash
+aio app deploy --force-deploy
+```
+
+To update the credentials or services used by an already published application, you must revoke it and go through the approval process again.
 
 1. Ask an enterprise organization administrator to revoke your published application in the [Adobe Exchange Manage panel](https://exchange.adobe.com/manage). Note that once revoked, your application will no longer be public.
 

src/pages/events/api.md

@@ -140,3 +140,35 @@ curl -i -X PUT \
 }' \
  '<ADOBE_COMMERCE_URL>/rest/all/V1/eventing/updateConfiguration'
  ```
+
+## Get configured event provider information
+
+The `GET /rest/<store_view_code>/V1/eventing/getEventProviders` endpoint returns information about the event provider configured for the Commerce instance.
+
+**Headers:**
+
+`Authorization: Bearer <administrator token>`
+
+The administrator must be granted access to the `Magento_AdobeIoEventsClient::event_provider_list` resource.
+
+**Example usage:**
+
+The following cURL command retrieves information about the configured event provider:
+
+```bash
+curl -H "Authorization:Bearer <AUTH_TOKEN>" \
+'<ADOBE_COMMERCE_URL>/rest/all/V1/eventing/getEventProviders' \
+```
+
+**Example response:**
+
+```json
+[
+  {
+    "provider_id": "ad667bc6-1678-49ff-99fc-215d71ebf82f",
+    "instance_id": "my_instance",
+    "label": "my_provider",
+    "description": "Provides out-of-process extensibility for Adobe Commerce"
+  }
+]
+```

src/pages/events/convert-field-values.md

@@ -42,8 +42,8 @@ In the following example, the `TestConverterVisibility` converter class updates
 ```php
 <?php
 /**
- * Copyright &copy; Magento, Inc. All rights reserved.
- * See COPYING.txt for license details.
+ * Copyright [first year code created] Adobe
+ * All rights reserved.
  */
 declare(strict_types=1);
 

src/pages/events/custom-event-fields.md

@@ -74,8 +74,8 @@ In the following example, the `TestProcessorOrderStatus` class adds the `order_s
 ```php
 <?php
 /**
- * Copyright &copy; Magento, Inc. All rights reserved.
- * See COPYING.txt for license details.
+ * Copyright [first year code created] Adobe
+ * All rights reserved.
  */
 declare(strict_types=1);
 ​

src/pages/events/release-notes.md

@@ -12,6 +12,16 @@ These release notes describe the latest version of Adobe I/O Events for Adobe Co
 
 See [Update Adobe I/O Events for Adobe Commerce](installation.md#update-adobe-io-events-for-adobe-commerce) for upgrade instructions.
 
+## Version 1.10.0
+
+### Release date
+
+December 10, 2024
+
+### Enhancements
+
+* Added the `GET /rest/<store_view_code>/V1/eventing/getEventProviders` REST endpoint for retrieving information about the configured event provider. <!---CEXT-3913 -->
+
 ## Version 1.9.0
 
 ### Release date

src/pages/webhooks/index.md

@@ -27,7 +27,7 @@ The resolution of a remote call also determines whether you should implement a w
 
 Use these guidelines to develop your own webhooks:
 
-1. Identify the Adobe Commerce event that triggers a webhook. Adobe Commerce merchants can browse the available events from the Admin by selecting **System** > Events > **Events** to display the Events list page.
+1. Identify the Adobe Commerce event that triggers a webhook. Adobe Commerce merchants can browse the available events from the Admin by selecting **System** > Events > **Events List** to display the Events list page.
 
 1. Understand the default payload of the corresponding webhook by running the [`bin/magento webhooks:info` command](commands.md#display-the-payload-of-a-webhook).
 

src/pages/webhooks/signature-verification.md

@@ -88,6 +88,27 @@ To verify the signature in the App Builder action, set the `raw-http` annotation
       raw-http: true
 ```
 
+Store the public key in the `PUBLIC_KEY` parameter in the `.env` file using the same format as provided in the Adobe Commerce Admin:
+
+```env
+# Other secrets and configuration
+# ...............................
+
+PUBLIC_KEY="-----BEGIN PUBLIC KEY-----
+MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtglXYVz5pVn3HDluGG5T
+t9coO5NKSWjx3xCDMHVa3CEqVM76PKg8UJH9fQOA57xoNv7Llc916pF0UswtudQh
+Fyg+WQCFFadqGZOyL2nUKI9xWBiUi4dN8+9yMd3TE1fszVUBnk/XdLKNDQn4O6ic
+doQZi5arrjNjInkimtcT2jPXs34p9G9P5CvCubPUmbGsWDgwo5an9LEX/nJfnCdZ
+R10XPkRWzEM7o1OGzf7CYo06Xl+msGVM02Er265PsMAWB11cWwKmyg6dLPa8q+Qh
+KNXZiEMvdVusV8aA6EkCZYFdWSBXv+jltn6NnY5qvYcuQ3SujQ9xKEANjeMWcW90
+PwIDAQAB
+-----END PUBLIC KEY-----"
+```
+
+**Note:** Do not commit the `.env` file to version control.
+
+[App Builder Configuration Files](https://developer.adobe.com/app-builder/docs/guides/configuration/#env) describes `.env` file usage in detail.
+
 The following code example below shows how the signature can be verified in the App Builder action:
 
 ```javascript
@@ -109,9 +130,20 @@ async function main (params) {
     if (isSignatureValid) {
       logger.info('The signature is valid.');
       // Here will be performed real action logic
-      operations.push({
-        op: 'success'
-      });
+      // payload is base64 encoded, so we need to decode it before using   
+      const payload = JSON.parse(atob(params.__ow_body))
+
+      // a simple validation if the provided postcode from Commerce webhook is less than 50000  
+      if (payload.address.postcode > 50000) {
+        operations.push({
+            op: 'exception',
+            message: 'The postcode is not allowed. Provided postcode: ' + payload.address.postcode
+        });
+      } else {
+        operations.push({
+            op: 'success'
+        });
+      }
     } else {
       logger.info('The signature is invalid.');
       operations.push({

yarn.lock

@@ -33,9 +33,9 @@ __metadata:
   languageName: node
   linkType: hard
 
-"@adobe/gatsby-theme-aio@npm:4.14.16":
-  version: 4.14.16
-  resolution: "@adobe/gatsby-theme-aio@npm:4.14.16"
+"@adobe/gatsby-theme-aio@npm:4.14.17":
+  version: 4.14.17
+  resolution: "@adobe/gatsby-theme-aio@npm:4.14.17"
   dependencies:
     "@adobe/focus-ring-polyfill": ^0.1.5
     "@adobe/gatsby-source-github-file-contributors": ^0.3.1
@@ -131,7 +131,7 @@ __metadata:
     gatsby: ^4.22.0
     react: ^17.0.2
     react-dom: ^17.0.2
-  checksum: 23efce4352fb14582a06f845362ec7cf242e66db49014d2dc6e39c70efdcc2f40265b0c9f17cc55cb96a6cde828f3456b9d9edea5f80fa9ca56f5d8260d0d2e6
+  checksum: 929ed9cc32b048ec243dbcd75be3ee822294946e336600bf57b67490632fcd0a0e375e4683a2980eb756b80ee023d5e9605dd91a6a6ebc910d6dac08530aee13
   languageName: node
   linkType: hard
 
@@ -7337,7 +7337,7 @@ __metadata:
   version: 0.0.0-use.local
   resolution: "commerce-extensibility@workspace:."
   dependencies:
-    "@adobe/gatsby-theme-aio": 4.14.16
+    "@adobe/gatsby-theme-aio": 4.14.17
     gatsby: 4.22.0
     react: ^17.0.2
     react-dom: ^17.0.2
@@ -7695,15 +7695,15 @@ __metadata:
   linkType: hard
 
 "cross-spawn@npm:^6.0.0, cross-spawn@npm:^6.0.5":
-  version: 6.0.5
-  resolution: "cross-spawn@npm:6.0.5"
+  version: 6.0.6
+  resolution: "cross-spawn@npm:6.0.6"
   dependencies:
     nice-try: ^1.0.4
     path-key: ^2.0.1
     semver: ^5.5.0
     shebang-command: ^1.2.0
     which: ^1.2.9
-  checksum: f893bb0d96cd3d5751d04e67145bdddf25f99449531a72e82dcbbd42796bbc8268c1076c6b3ea51d4d455839902804b94bc45dfb37ecbb32ea8e54a6741c3ab9
+  checksum: a6e2e5b04a0e0f806c1df45f92cd079b65f95fbe5a7650ee1ab60318c33a6c156a8a2f8b6898f57764f7363ec599a0625e9855dfa78d52d2d73dbd32eb11c25e
   languageName: node
   linkType: hard