[Feature] Allow organization and brand to be enable/disable configurable

[fivetran-joemarkiewicz]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

I've found a number of cases where users do not have the organization or brand tables syncing from their Zendesk connector. We should support the Zendesk package to run without error when these two tables are not present in the destination.

How would you implement this feature?

Add two new variables using_organization and using_brand for both zendesk and zendesk_source to leverage when planning the models and turning off these components when the variable (default true) is set to disabled.

As an added benefit, we will be able to add this to the quickstart.yml so the Quickstart orchestration method can handle this enable/disable mechanism entirely.

Describe alternatives you've considered

Adding the union data feature will address this issue, but it could introduce other issues as well. Adding these variables will more accurately address this issue.

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance.
• No.

Anything else?

I also noticed that some customers experience runtime failures due to the ticket_field_history table not being present. However, since this is a core table for many downstream models I would prefer we do not add a enable/disable mechanism for this table. Although we can always keep a close eye on this to see if this is something to consider in the future.