Skip to content

Enable container scanning on CI

Tan Le requested to merge 300-enable-container-scanning-second-try into main

What does this merge request do and why?

This MR is a second attempt to enable container scanning on CI.

The initial attempt broke the runway deploy (build ref) due to a bug in variable expansion. The image_id was not set (ref).

  # docker_image.gitlab_registry_image has been deleted
  - resource "docker_image" "gitlab_registry_image" {
        id          = "sha256:06d262558ef540b5263f04303ef22638447b9cbb8a82f4d1ee10fcf2a4abbc9dregistry.gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/model-gateway:ec9773d4"
      - image_id    = "sha256:06d262558ef540b5263f04303ef22638447b9cbb8a82f4d1ee10fcf2a4abbc9d" -> null
        name        = "registry.gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/model-gateway:ec9773d4"
        # (1 unchanged attribute hidden)
    }

The difference between this MR and the initial one is that the inputs.image variable is left unchanged, ie. not replaced by TARGET_IMAGE variable (ref)

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request checklist

  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.

Closes #300 (closed)

Edited by Tan Le

Merge request reports