Ignore fields so that a pull doesn't change them. This is useful when a field differs by design between an original integration and its clone. Ignoring applies to the whole integration, not to one flow or resource. For example, ignoring flow descriptions ignores the description of every flow.
ILM supports ignored fields for integrations that contain flows, APIs, or both.
What you can ignore
You can ignore common fields in these resources:
- Integrations
- Flows
- Exports
- Imports
- Lookup caches
- Scripts
- Settings (custom)
- Hooks
- Transformations
- Filters
- Mappings
- APIs
Some details:
- Lookup caches — To ignore lookup caches, select the lookup field under imports or exports. This ignores all lookups, not only lookup caches.
- Mappings — Selecting mappings ignores all fields and lists in your mapping configuration. You can't ignore one mapping or one mapping configuration.
-
APIs — You can ignore
name,description, andversion. An ignored API field applies to all APIs in the integration.relativeURIandmethodaren't available at the API level.
Ignoring a field ignores updates to that field. It doesn't ignore the creation or deletion of resources. You can't ignore:
- An individual flow, export, import, or script.
- An individual field in your data, as opposed to a common form field.
- A newly created or deleted flow, export, import, or script.
Why ignore fields
- A field varies between the original and the clone. For example, a relative URI can differ between a non-production and a production integration.
- You aren't done testing a change to a field and don't want it to reach production.
- You want to test how excluding a resource type, such as filters or scripts, affects the integration.
- You want to prevent an API version difference from blocking a pull between environments. See Troubleshoot ILM revision and pull issues.
Ignore fields
You can ignore every available field under a resource, or only one field. For example, ignoring all integration fields covers name, description, and the others. Ignoring only description leaves the rest.
- Go to Revisions, and then select Ignore fields during pull.
- Search for or select the resources or fields to ignore. If you select a resource such as transformation or filter, integrator.io selects every field under it.
- Select Done.
- Select Save & close. Select Save to keep the panel open.
If an original integration ignores a field, a pull to its clone doesn't include that field. For example, if the original ignores the integration description and you create a pull to Clone A, the description isn't included in the pull.
Remove fields from the ignore list
- Go to Revisions, and then select Ignore fields during pull.
- Clear each field you want to stop ignoring.
- Select Save & close.
Remove deleted fields from the ignore list
If you delete a resource that has fields on the ignore list, remove those fields from the list. ILM functions keep working, but the fields appear in red when you reopen the list. For example, you ignore all import fields and later delete every import. The import fields are now invalid. If other resources of the same kind still exist, you don't see this warning.
- Go to Revisions, and then select Ignore fields during pull.
- Clear each field highlighted in red.
- Select Save & close.