Skip to content

Commit

Permalink
Apply suggestions from code review
Browse files Browse the repository at this point in the history
  • Loading branch information
jhadobe authored Jun 12, 2024
1 parent 358ad69 commit 81de9eb
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/pages/events/commands.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,9 +136,9 @@ The `events:metadata:populate` command creates event metadata based on XML and a

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`.
* 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

0 comments on commit 81de9eb

Please sign in to comment.