If the omitInactive option is disabled in your environment configuration, you may end up fetching a large number of inactive elements. These inactive elements can differ across environments, leading to inconsistencies and a higher number of differences. By default, omitInactive is set to true, which stops inactive elements from being fetched and helps streamline your environment.
However, you can customize this behavior further based on your needs:
Customizing omitInactive for Specific Types
To omit inactive elements for a specific type, add the following to your environment configuration file. For example, to omit inactive triggers:
zendesk {
fetch = {
omitInactive = {
customizations = {
trigger = true
}
}
}
}
Customizing omitInactive for all types
To omit inactive elements from all types, add the following configuration to you environment configuration file (See "Important Note for exceptions).
zendesk {
fetch = {
omitInactive = {
default = true
}
}
...
}
Important Note About ticket forms
Even if omitInactive is set to true, inactive instances of the ticket forms type will still be fetched. This behavior ensures consistency with ticket form order, as not fetching inactive ticket forms could lead to issues with ordering.
This flexibility allows you to control the fetching of inactive elements to suit your specific requirements while maintaining necessary data integrity in certain cases.