Skip to content

Fix a case where a change to a project in terraform can never apply w…

Paulius Laurinavicius requested to merge github/fork/olhado/send_project_name_on_update into main

Created by: olhado

…hen certain fields are modified.

Because the gitlab API actually expects at least on field out of a subset of fields in an update call (aside from id), if you only modify fields not in this subset, the Gitlab API will return a 400 complaining that one of the needed fields is missing.

One of these special fields is name. As this seems to be a safe field to assume always exists (we'll still defensively check if nil though), we pass it in always.

Description

#1157 (closed)

  • [ X] 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.)

Merge request reports