Configuration lets you manage versioned settings for an integration. Each change creates a new revision, which preserves a history of which configuration was active. Extractors fetch the active revision at startup. Each check-in response notifies the extractor of newer revisions.
Integration configuration is a revisioned document associated with an integration. Every time you push a new configuration, CDF stores it as a new revision rather than overwriting the previous one. This lets you audit configuration changes and know exactly which revision an extractor was running at any point in time.
Managing configuration revisions
You create a new configuration revision when you want to change how an extractor behaves. You can list all revisions for an integration to review its configuration history, or retrieve a specific revision, the revision that was active at a timestamp you specify, or the revision an extractor currently reports using.
Configuration revisions are immutable once created. To change behavior, create a new revision rather than editing an old one.
Key operations
- Create revision: Push a new configuration revision for an integration.
- List revisions: Review the configuration history for an integration.
- Retrieve: Get a specific revision, or the revision that was active at a timestamp you specify.
Versioned configuration ties together what an extractor is running with the task and error data it reports, so you can correlate behavior changes with configuration changes. 
