Overview
The Product Attribute Subscriber is a configuration-based subscriber that listens for product attribute data from a Magento 2 source system. It replaces the deprecated prototype-based magento-2-roduct-attribute-subscriber previously used in the Legacy Magento 2 Connector.
This component has been migrated from a prototype-based implementation to a configuration-based setup as part of the Legacy Magento 2 Connector replacement project.
Prototype vs Configuration-based
This is an important behavioral difference to understand before setting up this component.
| Prototype-based | Configuration-based |
|---|
| Reusability | Can be reused across different flows by changing a few fields | Not reusable across different purposes or payloads |
| Flexibility | One prototype can serve multiple use cases | (Not always) Each use case requires its own dedicated configuration |
| How to reuse | Modify fields directly | Duplicate the configuration and adjust as needed |
Type
Subscriber
Purpose
This Subscriber listens to Incoming product attribute data from Magento 2 and triggers the appropriate Route for further processing. It is used in flows where product attribute information needs to be synced or transformed to a target system.
Configuration
| Parameter | Description | Required |
|---|
store_code | The Magento 2 Store Code | Yes |
http-client | The HTTP Client Authentication method used to connect to Magento 2 | Yes |
entity-schema | The specific schema for the entity | No |
Usage
- Navigate to Subscribers in your Alumio environment.
- Search for Magento 2 Product Attribute Subscriber.
- Configure the required parameters as described above.
- Attach this Subscriber to the relevant route as the Incoming configuration.
Deprecated VS New
An example of the deprecated one:
An example of the new configuration:
- Magento 2 Product Attributes Subscriber (Transformer - Mapping) (Transformer) - to restructure the result.
Notes
- Replaces the prototype:
magento-2-product-attribute-subscriber
- Unlike the prototype-based implementation, this configuration-based Subscriber is not reusable across different purposes or payloads. If you need to handle a different payload structure or use case, you must duplicate this Subscriber and adjust the configuration accordingly.
- This Subscriber is typically used in product attribute sync flows.
