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

[BUG]: Trying to update provider from v5 to v6 fails with error #2266

Open
1 task done
nnellanspdl opened this issue May 17, 2024 · 0 comments
Open
1 task done

[BUG]: Trying to update provider from v5 to v6 fails with error #2266

nnellanspdl opened this issue May 17, 2024 · 0 comments
Labels
Status: Up for grabs Issues that are ready to be worked on by anyone Type: Bug Something isn't working as documented

Comments

@nnellanspdl
Copy link

Expected Behavior

Modify my code to support the new v6 syntax, and be able to run a plan and apply like normal.

Actual Behavior

I was previously using v5 of the provider. I updated my code to use v6. I also updated my code to follow the new syntax for the github_branch_protection resource. However, when I run a Plan I get the error below.

It is very similar to this issue which discusses going from v4 to v5. Looks like you had to add some sort of migration to the backend.

Can you please apply the same fix here?

Warning: Failed to decode resource from state
Error decoding
github_branch_protection
from prior state: unsupported attribute "blocks_creations"

Terraform Version

Terraform 1.5.7

Affected Resource(s)

  • github_branch_protection

Terraform Configuration Files

No response

Steps to Reproduce

No response

Debug Output

No response

Panic Output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@nnellanspdl nnellanspdl added Status: Triage This is being looked at and prioritized Type: Bug Something isn't working as documented labels May 17, 2024
@kfcampbell kfcampbell added Status: Up for grabs Issues that are ready to be worked on by anyone and removed Status: Triage This is being looked at and prioritized labels Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Up for grabs Issues that are ready to be worked on by anyone Type: Bug Something isn't working as documented
Projects
None yet
Development

No branches or pull requests

2 participants