Fix group membership resource error when user is removed outside of terraform

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

When a user is removed from a group outside of Terraform, the provider returns a 404 Not Found during the read. This fixes the problem by removing the resource from the state.

Closes #6446 (closed)

added devopsdeploy groupenvironments sectioncd typebug labels

added Leading Organization label

Thanks for your contribution to GitLab @mness!

• If you need help, page a coach by clicking here or come say hi on Discord.
• When you're ready, request a review by clicking here.
• We welcome AI-generated contributions and offer complimentary access to GitLab Duo!
• To add labels to your merge request, comment @gitlab-bot label ~"label1" ~"label2".

This message was generated automatically. Improve it or delete it.

added Community contribution workflowin dev labels

assigned to @mness

changed the description

	2 Warnings
	7ee2df5d: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.
	This merge request does not refer to an existing milestone.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@tigerwnz (UTC+13)	@PatrickRice (UTC+0)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added linked-issue label

@gitlab-bot ready @PatrickRice

added workflowready for review label and removed workflowin dev label

requested review from @PatrickRice

	1 Warning
	7ee2df5d: The commit subject may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Reviewer	Maintainer
@tigerwnz (UTC+13)	@PatrickRice (UTC+0)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

approved this merge request

@PatrickRice, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure we don't only run predictive pipelines, and we don't break master, please start a new pipeline before merging.

Please wait for the pipeline to start before resolving this discussion and set auto-merge for the new pipeline. See merging a merge request for more details.

added pipeline:mr-approved label

resolved all threads

started a merge train

changed milestone to %17.10

merged

mentioned in commit 8e5d3285

Hi @mness

See where you rank! Check your spot on the contributor leaderboard and unlock rewards.

---

How was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

As a benefit of being a GitLab Community Contributor, you have access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.

Thanks for your help!

This message was generated automatically. Improve it or delete it.