Configuration Changes
Core stores configuration change history in PostgreSQL. REST controllers and GraphQL datafetchers record successful user changes through CoreAuditLogger. No separate collector or container is required.
The supported types are FLOW, PLUGIN, ARTIFACT, SITE_SETTING, and LOOKUP_TABLE.
For core database mutations, the update and history record share a transaction: both commit or both roll back. Failed operations and results indicating no change are not recorded. Lookup tables use a separate datasource, and artifact storage and deployments involve external services; these changes are recorded after success on a best-effort basis. A history write failure is logged and does not reverse an external change.
Each record includes an ID, Unix millisecond timestamp, type, operation, resource identifier, actor, and operation-specific metadata. Metadata may include item names, counts, versions, aliases, byte sizes, and artifact SHA-256 checksums. Property and variable values, lookup rows, credentials, and artifact contents are excluded. Only metadata explicitly selected by the API handler is recorded.