Resolve "`gitlab_group_label`: change ID to support passthrough importer"

Closes #1056 (closed)

changed milestone to %16.0

added Category:Terraform provider breaking change devopsdeploy groupenvironments sectionops workflowready for development labels

@timofurrer thanks for adding the breaking change label!

This merge request introduces breaking changes. Learn more about breaking changes.

It's important to identify how the breaking change was introduced. To estimate the impact, try to assess the following:

• Are there existing users depending on this feature?
  • Are self-managed customers affected?
  • To verify and quantify usage, use Grafana or Kibana.
  • If you're not sure about how to query the data, contact the infrastructure team on their Slack channel, #infrastructure-lounge
• Was sufficient time given to communicate the change?
• Changes in the permissions, the API schema, and the API response might affect existing 3rd party integrations.
  • Reach out to the Support team or Technical Account Managers and ask about the possible impact of this change.

This message was generated automatically. You're welcome to improve it.

added 1 commit

• 31679a82 - resource/gitlab_group_label: change id format to `<group>:<label>`

Compare with previous version

marked this merge request as ready

assigned to @timofurrer

added maintenancerefactor workflowready for review labels and removed workflowready for development label

requested review from @PatrickRice

added typemaintenance label

	1 Error
	The merge request title may not be longer than 72 characters. For more information, take a look at our Commit message guidelines.

	2 Warnings
	31679a82: The commit subject must start with a capital letter. For more information, take a look at our Commit message guidelines.
	31679a82: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. 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
No reviewer available	No maintainer available

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 is approved. To ensure full test coverage, a new pipeline will be started shortly.

For more info, please refer to the following links:

• rspec predictive jobs
• jest predictive jobs
• merging a merge request.

added pipeline:mr-approved label

enabled an automatic merge when the pipeline for 85f72d89 succeeds

merged

mentioned in commit 87cfa6b9