Skip to content
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

Jump to bottom

CEXT-3302: Adding additional events:metadata:populate info #224

Merged
merged 6 commits into from
Jun 12, 2024
Merged

CEXT-3302: Adding additional events:metadata:populate info #224

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
22d3f63
CEXT-3302: Adding additional events:metadata:populate info
ryanjcohen Jun 11, 2024
b9b57c5
CEXT-3302: Adding mention of manual config.php edits
ryanjcohen Jun 11, 2024
df5a5eb
Apply suggestions from code review
jhadobe Jun 12, 2024
d9b620a
Apply suggestions from code review
jhadobe Jun 12, 2024
358ad69
Merge branch 'main' into CEXT-3302-events-metadata-populate
jhadobe Jun 12, 2024
81de9eb
Apply suggestions from code review
jhadobe Jun 12, 2024
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
8 changes: 7 additions & 1 deletion src/pages/events/commands.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,13 @@ bin/magento events:registrations:list -vv

## Create event metadata in Adobe I/O

The `events:metadata:populate` command creates event metadata based on XML and application configurations.
The `events:metadata:populate` command creates event metadata based on XML and application configurations. This metadata gets linked to the configured event provider.

Event metadata is automatically created for new event subscriptions when you run the [`events:subscribe` command](#subscribe-to-an-event) and synchronize events registered in `io_events.xml` files or `config.php` when the `setup:upgrade` command runs. In the following situations, we recommend creating event metadata using the `events:metadata:populate` command:

* You have configured an event provider after an `io_events.xml` file was pushed to your cloud instance and a redeployment has not occurred since this change.
* You have not run `setup:upgrade` since adding an `io_events.xml` file to your on-premise instance.
* You manually edited the event subscriptions configuration in `app/etc/config.php`.

### Usage

Expand Down
Loading