Merge branch 'main' into CEXT-3814

Author: keharper

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

@@ -33,3 +33,9 @@ The following sequence diagram illustrates the authentication process.
 ## Code samples
 
 The [Adobe Commerce Samples repository](https://github.com/adobe/adobe-commerce-samples/tree/main/admin-ui-sdk) contains samples for different extension points of the Adobe Commerce Admin UI SDK. Use these samples to gain insight on how the Admin SDK injects menus and pages into the Admin.
+
+## Admin UI SDK and Adobe Extensions
+
+Adobe App Builder supports [extensions](https://developer.adobe.com/app-builder/docs/guides/extensions/), which allow developers to integrate their applications with specific Adobe products, such as the Admin UI SDK. Extensions act as a bridge between Adobe products and the applications built using Adobe App Builder. As a result, these applications can be easily integrated and extended within Adobe's ecosystem.
+
+App Builder projects support `application` and `extension` configurations within the `app.config.yaml` file. The Admin UI SDK supports both of these types as well. The SDK is not affected if you [migrate](https://developer.adobe.com/app-builder/docs/guides/extensions/extension_migration_guide/) an existing App Builder project that uses an `application` configuration to use an `extension` configuration.

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/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).
 

yarn.lock

@@ -15352,11 +15352,11 @@ __metadata:
   linkType: hard
 
 "nanoid@npm:^3.3.4":
-  version: 3.3.4
-  resolution: "nanoid@npm:3.3.4"
+  version: 3.3.8
+  resolution: "nanoid@npm:3.3.8"
   bin:
     nanoid: bin/nanoid.cjs
-  checksum: 2fddd6dee994b7676f008d3ffa4ab16035a754f4bb586c61df5a22cf8c8c94017aadd360368f47d653829e0569a92b129979152ff97af23a558331e47e37cd9c
+  checksum: dfe0adbc0c77e9655b550c333075f51bb28cfc7568afbf3237249904f9c86c9aaaed1f113f0fddddba75673ee31c758c30c43d4414f014a52a7a626efc5958c9
   languageName: node
   linkType: hard