chore(deps): update dependency uis/devops/continuous-delivery/ci-templates to v6 - autoclosed (!6) · Merge requests · Information Services / DevOps / Experiments / Example Python CLI tool

uis-devops-renovatebot requested to merge renovate/uis-devops-continuous-delivery-ci-templates-6.x into main Oct 30, 2024

This MR contains the following updates:

Package	Type	Update	Change
uis/devops/continuous-delivery/ci-templates	repository	major	`v2.2.1` -> `v6.0.2`

Release Notes

uis/devops/continuous-delivery/ci-templates (uis/devops/continuous-delivery/ci-templates)

Changed

Remove allow_failure: true from commitlint and commitlint-hotfix jobs. This behaviour is no longer desirable as we've built our whole release-it process around the conventionalcommits specification. It's now more beneficial for these jobs to fail by default.

`v4.1.0`

Compare Source

Added

A generic get-gcp-secrets fragment to retrieve one or more Google Secret Manager secrets in a CI job.

`v4.0.0`

Compare Source

Changed

BREAKING CHANGE: removed legacy /auto-devops/terraform-deployment.yml and /auto-devops/terraform-lint.yml templates as these should not be being used any more.
Refactored /auto-devops/terraform-pipeline.yml template so that the hidden "template" jobs are now in their own /terraform-pipeline-base.yml template file. This allows more flexibility for some projects which do not/cannot follow the standard three-environment deployment defined in the /auto-devops/terraform-pipeline.yml template.
Refactored the Terraform testing/linting jobs into their own /terraform-lint.yml template. This is useful for projects which are not being deployed via CI/CD but which we do want to test in a pipeline.

`v3.8.2`

Compare Source

Fixed

terraform-pipeline.yml: tflint rule terraform_standard_module_structure is now disabled.

`v3.8.1`

Compare Source

Fixed

terraform-pipeline.yml: tflint job updated and now compatible with tflint v0.40.0+

`v3.8.0`

Compare Source

Changed

terraform-pipeline.yml: tfsec job replaced with trivy as tfsec is now deprecated.

`v3.7.1`

Compare Source

Fixed

artifact-registry.yml: added before_script to fix "docker in docker" service startup.

`v3.7.0`

Compare Source

Added

artifact-registry.yml: add support for code repositories with multiple apps.

`v3.6.1`

Compare Source

Fixed

check_latest_tag_in_changelog now correctly identifies the latest tag in the CHANGELOG, when there isn't a space after the closing square bracket.

`v3.6.0`

Compare Source

`v3.5.0`

Compare Source

`v3.4.0`

Compare Source

`v3.3.0`

Compare Source

Fixed

terraform-pipeline.yml: allow plan and apply jobs to run on git tag actions.

Added

terraform-pipeline.yml: add TF_PLAN_TARGET variable to allow targeted plan actions.

`v3.2.0`

Compare Source

`v3.1.1`

Compare Source

`v3.1.0`

Compare Source

Added

commitlint.yml template to ensure the Conventional Commits standard is adhered to for projects who wish to use it.

`v3.0.0`

Compare Source

`v2.7.0`

Compare Source

Added

terraform-module: Extend the GitLab Terraform Module to ensure the tag being used to version the module exists in the CHANGELOG.

`v2.6.2`

Compare Source

Fixed

pre-commit.yml: relax pre-commit job rules to enable users to decide when to include the job via workflow rules instead.

`v2.6.1`

Compare Source

Fixed

artifact-registry: fix issue with $DOCKER_CERT_PATH containing the $DOCKER_TLS_CERTDIR variable. We've seen multiple issues with this variable expanding as an empty value. Instead, we're simply hard coding it instead which appears to have resolved the issue.

`v2.6.0`

Compare Source

Added

terraform-pipeline: Allow the tfsec job to exclude specific checks. This is useful to exclude a default list of checks that we don't follow in the boilerplate.

Fixed

artifact-registry: Allow manual push to registry for non-default branches. This is useful for testing container images from feature branches. However, to avoid littering the artifact registry with endless feature branch containers, it is configured as a manual job.
terraform-pipeline: Allow the development apply job to fail. This is currently the only way to allow the whole pipeline to show as succeeded if the (optional) development apply job has not been triggered. Otherwise, the pipeline shows as blocked, which is confusing. See the following issue for context https://gitlab.com/gitlab-org/gitlab/-/issues/249524.