Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: no schema available for module.dbt-jobs-utility.dbt_cloud_job.uat_job while reading state; this is a bug in Terraform and should be reported #333

Open
prai-bv opened this issue Jan 23, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@prai-bv
Copy link

prai-bv commented Jan 23, 2025

Terraform Plan is showing this error.

we have updated from old https://github.com/dbt-labs/terraform-provider-dbtcloud/blob/main/README.md to https://github.com/dbt-labs/terraform-provider-dbtcloud and after that

Whenever we face these issues: Error: no schema available for module.dbt-jobs-utility.dbt_cloud_job.uat_job while reading state; this is a bug in Terraform and should be reported

We have followed every step provided in the old Terraform provider of dbt while migrating to new terraform dbt provider.

@prai-bv prai-bv added the bug Something isn't working label Jan 23, 2025
@b-per
Copy link
Collaborator

b-per commented Jan 23, 2025

Do you mean that you moved from the dbt_cloud_xxx resources to the dbtcloud_xxx ones? like described here?

The instructions were written for and tested when people are not using modules but we have not tested it when the config is in some modules.

Searching online, it seems to be an issue that some people have been having with changing versions for different providers (here for example, I also found other threads), so this is not really something we can fix on this provider side.

I would recommend to backup your config and state before the move to the new provider and then look online at how people have solved this issue. It might involve manually updating your state file.

We can keep this open for a bit if you have specific questions but there is nothing we can update/fix on the provider side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants