Not all models include the enabled config
- Dominant language
- No language data
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Describe the issue
Currently, the package expects certain sources to be available. Some models, but not all, include the enabled config, which makes it possible to skip the model if the source is not available. For example, `stg_zuora__credit_balance_adjustment` includes the following: `{{ config(enabled=var('zuora__using_credit_balance_adjustment', true)) }}` (code [here](https://github.com/fivetran/dbt_zuora_source/blob/main/models/stg_zuora__credit_balance_adjustment.sql#L1)). Of the 19 models, only 4 can be disabled:
- stg_zuora__credit_balance_adjustment
- stg_zuora__refund
- stg_zuora__refund_invoice_payment
- stg_zuora__taxation_item
At Pleo, we are not ingesting all the sources that are expected by the package, so even when leveraging the enabled config in the models where it's available, we are still left with models raising errors.
With the changes in [this PR](https://github.com/fivetran/dbt_zuora_source/pull/12), it is possible to disable any model, not just the subset listed above. Having the ability to disable models for which the sources are not ingested via Fivetran is a great feature, and it opens up use of this package even when only a few Fivetran sources are available.
### Relevant error log or model output
_No response_
### Expected behavior
I would expect to be able to leverage the package for as many models as we currently ingest via Fivetran. IOW, I would expect to be able to configure each model to be enabled.
Before making the changes, we had four models that raised errors because the sources are not available. I ran `dbt build --select +zuora_source` and the following shows the error:

After making the changes and disabling the models for sources we do not ingest, I ran `dbt build --select +zuora_source` again; no errors were raised.


I then removed one of the new variables to ensure that it still correctly raised an error; it did:

Note: `zuora__using_contact: false` is commented out.

### dbt Project configurations
```
zuora__using_credit_balance_adjustment: false
zuora__using_refund: false
zuora__using_refund_invoice_payment: false
zuora__using_taxation_item: false
```
### Package versions
```
- package: fivetran/zuora_source
version: [">=0.2.0", "<0.3.0"]
```
### What database are you using dbt with?
bigquery
### dbt Version

### Additional Context
I made and tested the changes in [this PR](https://github.com/fivetran/dbt_zuora_source/pull/12).
### Are you willing to open a PR to help address this issue?
- [X] Yes.
- [ ] Yes, but I will need assistance and will schedule time during our [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance
- [ ] No.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.