Skip to content

Upgrade `Terraform.gitlab-ci.yml` template to `Terraform.latest.gitlab-ci.yml` for 16.0

For guidance on the overall deprecations, removals and breaking changes workflow, please visit Breaking changes, deprecations, and removing features

Deprecation Summary

The currently stable Terraform.gitlab-ci.yml CI template should be replaced with the latest Terraform.latest.gitlab-ci.yml template as per our documentation.

This is a potential breaking change depending on how users have been using the template.

We must also bump the used terraform-images job image to the latest version.

Breaking Change

New Job Rules

All job templates (except deploy and destroy) contain at least the rules:

rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
    - if: $CI_OPEN_MERGE_REQUESTS  # Don't add it to a *branch* pipeline if it's already in a merge request pipeline.
      when: never
    - if: $CI_COMMIT_BRANCH        # If there's no open merge request, add it to a *branch* pipeline instead.

which may change under which circumstances jobs are. For example if they are triggered as a downstream pipeline the above won't match.

Potential gitlab-terraform breaking changes

Not sure if there are breaking changes when upgrading gitlab-terraform per se ... The issues and MRs didn't make use of breaking change and the semantic version major is still 0 ...

Affected Topology

Affected Tier

  • Free
  • Premium
  • Ultimate

Checklists

Labels

  • This issue is labeled deprecation, and with the relevant ~devops::, ~group::, and ~Category: labels.
  • This issue is labeled breaking change if the removal of the deprecated item will be a breaking change.

Timeline

Please add links to the relevant merge requests.

  • As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: 14.8, 14.9, 14.10, 15.0 – 14.8 is the third milestone preceding the major release):
  • On or before the major milestone: A removal entry has been created so the removal will appear on the removals by milestones page and be announced in the release post.
  • On the major milestone:

Mentions

  • Your stage's stable counterparts have been @mentioned on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.
    • To see who the stable counterparts are for a product team visit product categories
      • If there is no stable counterpart listed for Sales/CS please mention @timtams
      • If there is no stable counterpart listed for Support please mention @gitlab-com/support/managers
      • If there is no stable counterpart listed for Marketing please mention @cfoster3
  • Your GPM has been @mentioned so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

Planned Removal Milestone

Links

Edited by João Alexandre Cunha