Moving a subgroup does not force a recreation of the group and no longer deletes the underlying projects

Paulius Laurinaviciusrequested to merge
github/fork/gro-gg/main into main

Created by: gro-gg

Description

fixes #574 (closed)

PR Checklist Acknowledgement

  • I acknowledge that all of the following items are true, where applicable:
    • Resource attributes match 1:1 the names and structure of the API resource in the GitLab API documentation.
    • Examples are updated with:
      • A *.tf file for the resource/s with at least one usage example
      • A *.sh file for the resource/s with an import example (if applicable)
    • New resources have at minimum a basic test with three steps:
      • Create the resource
      • Update the attributes
      • Import the resource
    • No new //lintignore comments were copied from existing code. (Linter rules are meant to be enforced on new code.)

Tests

To test that the nested group is not recreated, I misused the AutoDevopsEnabled attribute. It ensures that the value is still true after transferring the nested group. If the group was recreated, it would be false again (default value). Please let me know if you have a better idea how to test this.

Merge request reports