Skip to content

Commit baa7d3c

Browse files
julitafalconduszamnocon
authored andcommitted
Fixes in "CDP data export schedule" page (#2363)
* Fixes in CDP data export page * typo fix * Fix
1 parent e7e49f4 commit baa7d3c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/cdp/cdp_data_export_schedule.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,9 +40,9 @@ ibexa_cdp:
4040
Under the `schedule` setting you can find separate sections for exporting user, content, and product.
4141
Structure of each section is exactly the same and includes `interval` and `options` elements:
4242

43-
- **Interval** - sets the frequency of the command invoke, for example, '*/30 * * * *' means "every 30 minutes", '0 */12 * * *' means "every 12 hours".
43+
- `interval` - sets the frequency of the command invoke, for example, '*/30 * * * *' means "every 30 minutes", '0 */12 * * *' means "every 12th hour".
4444
It uses a standard `crontab` format, see [examples](https://crontab.guru/examples.html).
45-
- **Options** - allows you to add arguments that have to be passed to the export command.
45+
- `options`- allows you to add arguments that have to be passed to the export command.
4646

4747
This configuration allows you to provide multiple export workflows with parameters.
4848
It's important, because each type of content/product must have its own parameters on the CDP side, where each has a different Stream ID key and different required values, which are configured per data source.
@@ -65,4 +65,4 @@ php bin/console ibexa:cdp:stream-product-data --help
6565

6666
```bash
6767
php bin/console ibexa:cdp:stream-content-data --help
68-
```
68+
```

0 commit comments

Comments
 (0)