[RecordingSettings]
Available since Exponential 6.0.15 (in development, not in a release yet).
Summary
The group [RecordingSettings] of settings/migration.ini.
File
settings/migration.ini; override it in settings/override/migration.ini.append.php, in a siteaccess or in an extension.
Settings
| Setting | Default | Description |
|---|---|---|
| Recording | enabled | Recordings of changes (./console exp:migration:record:start, Setup > Migrations > Recording): what is changed in the administration, the website sidebar or a command while a recording runs is kept as the steps of a YAML migration, for ./console exp:migration:generate --from-recording=<id>. A session recording keeps one user's own changes; a site-wide recording keeps every change of every user. The recording sees the kernel's operations (content published, a node moved, a class stored, a role changed, a setting written ...), not web requests. disabled: nothing is recorded and no recording can be started. |
| EventList[] | (empty array) | The audit events a recording keeps, by name (the kernel's audit taxonomy). Empty: every event a migration step can repeat (the list of expMigrationRecordingEvent::STEPS, in guides/migrations-generators-and-recording.md). |
| UserKeepAttributeList[] | (empty array) | The attributes of user objects that are not personal data and may be recorded (identifiers, e.g. a "signature" a site uses for a team account). Empty: none. The account (login, e-mail, password) is never recorded, whatever this says: a generated migration names it by a secret reference. |
| MaxEvents | 10000 | The most events one recording keeps; the recording keeps running but adds nothing more, and says so. 0: no limit. |
See also
Generated example: migration.ini [RecordingSettings]
Added to the reference for Exponential 6.0.15: the 4.x reference had no page for this group. The descriptions are the comment lines of settings/migration.ini.
Contributors
- Graham Brookins Updated
Comments
Add a comment