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

fix: Fixing enterprise_id import on github_enterprise_actions_permissions #2274

Merged
merged 2 commits into from
Jun 17, 2024

Conversation

ErikElkins
Copy link
Contributor

Resolves issue where enterprise_id wasn't getting imported as mentioned here: #2155 (comment)


Before the change?

  • The enterprise_id field wasn't getting set in state as a part of the import process of the github_enterprise_actions_permissions resource. Also, github/resource_github_enterprise_actions_runner_group_test.go was misspelled.

After the change?

  • The github_enterprise_actions_permissions now uses the enterprise_slug field to align with resource_github_enterprise_actions_runner_group and other enterprise resources, and sets it as a part of the import process.

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@ErikElkins ErikElkins changed the title fix: Fixing enterprise id reference fix: Fixing enterprise_id import May 28, 2024
@ErikElkins ErikElkins changed the title fix: Fixing enterprise_id import fix: Fixing enterprise_id import on github_enterprise_actions_permissions May 28, 2024
@kfcampbell
Copy link
Member

@ErikElkins thanks for the contribution! I'm torn about the breaking change here -- since the behavior was broken in the first place, I wonder if it's okay to release the schema change without a corresponding major version bump, since Hashicorp is pretty clear that releasing major versions too frequently is a bad idea: "To allow practitioners sufficient time and opportunity to upgrade to the latest version of the provider, we recommend releasing major versions no more than once per year. Releasing major versions more frequently could present a barrier to adoption due to the effort required to upgrade."

What do you think?

@ErikElkins
Copy link
Contributor Author

Yeah I think it's fair to avoid the major version change. It's probably only me and the one other commenter using this resource right now.

@kfcampbell kfcampbell merged commit 2a17feb into integrations:main Jun 17, 2024
3 checks passed
kireque referenced this pull request in kireque/home-ops Jul 9, 2024
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [github](https://registry.terraform.io/providers/integrations/github)
([source](https://togithub.com/integrations/terraform-provider-github))
| required_provider | patch | `6.2.2` -> `6.2.3` |

---

### Release Notes

<details>
<summary>integrations/terraform-provider-github (github)</summary>

###
[`v6.2.3`](https://togithub.com/integrations/terraform-provider-github/releases/tag/v6.2.3)

[Compare
Source](https://togithub.com/integrations/terraform-provider-github/compare/v6.2.2...v6.2.3)

<!-- Release notes generated using configuration in .github/release.yml
at main -->

#### What's Changed

##### 🛠️ Maintenance

- build(deps): bump the github-actions group with 2 updates by
[@&#8203;dependabot](https://togithub.com/dependabot) in
[https://github.com/integrations/terraform-provider-github/pull/2303](https://togithub.com/integrations/terraform-provider-github/pull/2303)

##### 🏷 Other Changes

- fix: Fixing `enterprise_id` import on
`github_enterprise_actions_permissions` by
[@&#8203;ErikElkins](https://togithub.com/ErikElkins) in
[https://github.com/integrations/terraform-provider-github/pull/2274](https://togithub.com/integrations/terraform-provider-github/pull/2274)
- Bump go-github to v62 + fixes by
[@&#8203;EttoreFoti](https://togithub.com/EttoreFoti) in
[https://github.com/integrations/terraform-provider-github/pull/2304](https://togithub.com/integrations/terraform-provider-github/pull/2304)
- docs: mark enterprise runner visibility required by
[@&#8203;gustavlasko](https://togithub.com/gustavlasko) in
[https://github.com/integrations/terraform-provider-github/pull/2278](https://togithub.com/integrations/terraform-provider-github/pull/2278)

#### New Contributors

- [@&#8203;gustavlasko](https://togithub.com/gustavlasko) made their
first contribution in
[https://github.com/integrations/terraform-provider-github/pull/2278](https://togithub.com/integrations/terraform-provider-github/pull/2278)

**Full Changelog**:
integrations/terraform-provider-github@v6.2.2...v6.2.3

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Renovate
Bot](https://togithub.com/renovatebot/renovate).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjYuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQyNi4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZS90ZXJyYWZvcm0iLCJ0eXBlL3BhdGNoIl19-->

Co-authored-by: kireque-bot[bot] <143391978+kireque-bot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants