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]: github_emu_group_mapping - Invalid address to set: []string{"group"} in v6 #2131

Closed
1 task done
gm-hyp-2 opened this issue Feb 7, 2024 · 3 comments
Closed
1 task done
Labels
Type: Bug Something isn't working as documented

Comments

@gm-hyp-2
Copy link

gm-hyp-2 commented Feb 7, 2024

Expected Behavior

Until v5.45.0 github_emu_group_mapping worked just fine. When upgrading to v6.0.0.0 and later, the resource cannot be used anymore.

Actual Behavior

When trying to run terraform plan on the resource github_emu_group_mapping: https://registry.terraform.io/providers/integrations/github/latest/docs/resources/emu_group_mapping it always breaks with this reason:

Error: Invalid address to set: []string{"group"}

  with github_emu_group_mapping.pure_fb_mapping["prague-object-one"],
  on teams.tf line 44, in resource "github_emu_group_mapping" "pure_fb_mapping":
  44: resource "github_emu_group_mapping" "pure_fb_mapping" {

Terraform Version

Terraform 1.7.2 on linux_amd64
Affected versions v6.0.0.0-alpha, v6.0.0.0-beta and v6.0.0.0-rc1

Affected Resource(s)

github_emu_group_mapping

Terraform Configuration Files

No response

Steps to Reproduce

Normal tf plan will highlight the error

Debug Output

No response

Panic Output

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@gm-hyp-2 gm-hyp-2 added Status: Triage This is being looked at and prioritized Type: Bug Something isn't working as documented labels Feb 7, 2024
@kfcampbell kfcampbell removed the Status: Triage This is being looked at and prioritized label Feb 7, 2024
@kfcampbell
Copy link
Member

This behavior should be fixed by #2133. In previous versions of the provider, we were ignoring that error. Can you please try v6.0.0-rc2 and report back to see if that fixes the error?

@gm-hyp-2
Copy link
Author

Yes, that PR seems to have resolved the issue. Thank you!

@kfcampbell
Copy link
Member

Sounds good! I'm going to close this issue for now. Thank you for reporting, and please reopen if it happens again.

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

No branches or pull requests

2 participants