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 2 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
10 changes: 9 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,15 @@ 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 the [`events:subscribe` command](#subscribe-to-an-event) is run and synchronized for events registered in `io_events.xml` files or `config.php` when the `setup:upgrade` command runs. Cases where creating event metadata using the `events:metadata:populate` command would be useful include the following:

jhadobe marked this conversation as resolved.
Show resolved Hide resolved
* 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

* You have not run `setup:upgrade` since adding an `io_events.xml` file to your on-premise instance
Copy link
Contributor

@oshmyheliuk oshmyheliuk Jun 11, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not a recommended way to manually edit app/etc/config.php but we can add:

You manually edited the events subscriptions configuration in `app/etc/config.php`

For example, It can happen during local development/testing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense, added it in


* You manually edited the event subscriptions configuration in `app/etc/config.php`
jhadobe marked this conversation as resolved.
Show resolved Hide resolved

### Usage

Expand Down
Loading