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

Issue with upgrading old projects to 3.0.1-rc1 version #933

Closed
sajjadG opened this issue Feb 10, 2024 · 6 comments
Closed

Issue with upgrading old projects to 3.0.1-rc1 version #933

sajjadG opened this issue Feb 10, 2024 · 6 comments
Labels

Comments

@sajjadG
Copy link

sajjadG commented Feb 10, 2024

Hello everyone, I wish you're having a good day.

When I use 3.0.1-rc1 for creating a new project it works. But when I upgrade my older projects to 3.0.1-rc1 version I get this error:

╷
│ Error: bool is required
│ 
│ 
╵

old project disk layout is the old one in tfstate file. I think that's the cause of this error.

@hestiahacker
Copy link
Contributor

This looks like the same thing that I fixed in #702 but it has not been merged into the default branch yet. #923

If you are willing to edit your tfstate file to replace "backup": 0 with "backup": false (or 1 with true) and try deploying again, that will confirm that this is the same issue. If it's some other field, please let me know.

The thing holding up the merge request is uncertainty as to whether we need to apply this fix to all fields that are booleans, so if you can confirm that the only one that is a problem is the "backup" field it might help get that merge request in sooner rather than later.

@hestiahacker
Copy link
Contributor

More detailed information about updating the tfstate file can be found in this comment

Copy link

This issue is stale because it has been open for 60 days with no activity. Please update the provider to the latest version and, in the issue persist, provide full configuration and debug logs

@github-actions github-actions bot added the stale label Apr 20, 2024
@hestiahacker
Copy link
Contributor

The merge request #923 has been merged into the default branch. When a v3.0.1-rc2 release candidate is cut, we can verify that it fixes this issue. The 3.x release is being tracked in #910 and #913.

@github-actions github-actions bot removed the stale label Apr 23, 2024
Copy link

This issue is stale because it has been open for 60 days with no activity. Please update the provider to the latest version and, in the issue persist, provide full configuration and debug logs

@github-actions github-actions bot added the stale label Jun 22, 2024
Copy link

This issue was closed because it has been inactive for 5 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants