Configuration revisions
Each pipeline can have multiple configuration revisions. Revisions are versioned, so you can track changes over time and roll back if needed. The active configuration is the one used by the extractor when it runs.Use cases
Use config management to update connection settings, change extraction parameters, or adjust schedules. Keep a revision history for audit trails and safe rollback. Revert to a previous revision if a new configuration causes issues.Configuration structure depends on the extractor. Retrieve the extractor’s schema to understand required and optional fields.
Key capabilities
- Create new revisions with updated configuration
- List revision history for a pipeline
- Retrieve specific revisions by ID
- Revert to previous configurations