2024-10-02 | MAIN --> PROD | DEV (4b5cd11) --> STAGING

[jadudm]

This is an auto-generated pull request to merge main into prod for a staging release on 2024-10-02 with the last commit being merged as 4b5cd11

[github-actions]

Source and image drift!
A PR stops confusion...
I got ya partner.

(...merge PR #4337...)

[github-actions]

Terraform plan for production

Plan: 1 to add, 2 to change, 1 to destroy.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.production.module.clamav.cloudfoundry_app.clamav_api will be updated in-place
!~  resource "cloudfoundry_app" "clamav_api" {
!~      docker_image                    = "ghcr.io/gsa-tts/fac/clamav@sha256:0bb13f065ce36beb9c0eb9531611a2a522aa5199f2bfbb107a9c2390f50d26e2" -> "ghcr.io/gsa-tts/fac/clamav@sha256:7f7d4e6edf21458675cfad17707206fce55bdb88079b15a4fecd2e20f34bb3d7"
        id                              = "5d0afa4f-527b-472a-8671-79a60335417f"
        name                            = "fac-av-production"
#        (17 unchanged attributes hidden)

#        (1 unchanged block hidden)
    }

  # module.production.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~      id       = "*******************" -> (known after apply)
!~      triggers = { # forces replacement
!~          "always_run" = "2024-09-25T17:33:33Z" -> (known after apply)
        }
    }

  # module.production.module.file_scanner_clamav.cloudfoundry_app.clamav_api will be updated in-place
!~  resource "cloudfoundry_app" "clamav_api" {
!~      docker_image                    = "ghcr.io/gsa-tts/fac/clamav@sha256:0bb13f065ce36beb9c0eb9531611a2a522aa5199f2bfbb107a9c2390f50d26e2" -> "ghcr.io/gsa-tts/fac/clamav@sha256:7f7d4e6edf21458675cfad17707206fce55bdb88079b15a4fecd2e20f34bb3d7"
        id                              = "6b0ce685-a80c-4feb-9ed6-49c6427efdb8"
        name                            = "fac-av-production-fs"
#        (17 unchanged attributes hidden)

#        (1 unchanged block hidden)
    }

Plan: 1 to add, 2 to change, 1 to destroy.

Warning: Argument is deprecated

  with module.domain.cloudfoundry_service_instance.external_domain_instance,
  on /tmp/terraform-data-dir/modules/domain/domain/main.tf line 45, in resource "cloudfoundry_service_instance" "external_domain_instance":
  45:   recursive_delete = var.recursive_delete

Since CF API v3, recursive delete is always done on the cloudcontroller side.
This will be removed in future releases

(and 6 more similar warnings elsewhere)

📝 Plan generated in Pull Request Checks #3717

[github-actions]

Terraform plan for staging

Plan: 1 to add, 2 to change, 1 to destroy.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # module.staging.module.clamav.cloudfoundry_app.clamav_api will be updated in-place
!~  resource "cloudfoundry_app" "clamav_api" {
!~      docker_image                    = "ghcr.io/gsa-tts/fac/clamav@sha256:0bb13f065ce36beb9c0eb9531611a2a522aa5199f2bfbb107a9c2390f50d26e2" -> "ghcr.io/gsa-tts/fac/clamav@sha256:7f7d4e6edf21458675cfad17707206fce55bdb88079b15a4fecd2e20f34bb3d7"
        id                              = "d1bea029-d2d3-4b68-b16d-b216bcaea573"
        name                            = "fac-av-staging"
#        (17 unchanged attributes hidden)

#        (1 unchanged block hidden)
    }

  # module.staging.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~      id       = "*******************" -> (known after apply)
!~      triggers = { # forces replacement
!~          "always_run" = "2024-09-27T19:06:32Z" -> (known after apply)
        }
    }

  # module.staging.module.file_scanner_clamav.cloudfoundry_app.clamav_api will be updated in-place
!~  resource "cloudfoundry_app" "clamav_api" {
!~      docker_image                    = "ghcr.io/gsa-tts/fac/clamav@sha256:0bb13f065ce36beb9c0eb9531611a2a522aa5199f2bfbb107a9c2390f50d26e2" -> "ghcr.io/gsa-tts/fac/clamav@sha256:7f7d4e6edf21458675cfad17707206fce55bdb88079b15a4fecd2e20f34bb3d7"
        id                              = "e416bb0c-8b95-47f7-9cff-c4029ebbd2df"
        name                            = "fac-av-staging-fs"
#        (17 unchanged attributes hidden)

#        (1 unchanged block hidden)
    }

Plan: 1 to add, 2 to change, 1 to destroy.

Warning: Argument is deprecated

  with module.staging-backups-bucket.cloudfoundry_service_instance.bucket,
  on /tmp/terraform-data-dir/modules/staging-backups-bucket/s3/main.tf line 14, in resource "cloudfoundry_service_instance" "bucket":
  14:   recursive_delete = var.recursive_delete

Since CF API v3, recursive delete is always done on the cloudcontroller side.
This will be removed in future releases

(and 6 more similar warnings elsewhere)

✅ Plan applied in Deploy to Staging Environment #278

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
18485	16840	91%	0%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 4b5cd11 by action🐍

[github-actions]

Source and image drift!
A PR stops confusion...
I got ya partner.

(...merge PR #4337...)

[github-actions]

Source and image drift!
A PR stops confusion...
I got ya partner.

(...merge PR #4337...)