Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024-07-31 | MAIN --> PROD | DEV (1bed165) --> STAGING #4138

Merged
merged 3 commits into from
Jul 31, 2024
Merged

2024-07-31 | MAIN --> PROD | DEV (1bed165) --> STAGING #4138

merged 3 commits into from
Jul 31, 2024

Conversation

jadudm
Copy link
Contributor

@jadudm jadudm commented Jul 31, 2024

This is an auto-generated pull request to merge main into prod for a staging release on 2024-07-31 with the last commit being merged as 1bed165

jadudm and others added 3 commits July 31, 2024 12:57
…ly) (#4080)

* Removing an offensive logging statement

* Add a newline, appease the linting gods

---------

Co-authored-by: James Person <[email protected]>
* Log UEI validation waivers on addition by admin

* Fix a typo in a comment
@jadudm jadudm added autogenerated Automated pull request creation automerge Used for automated deployments labels Jul 31, 2024
Copy link
Contributor

github-actions bot commented Jul 31, 2024

Terraform plan for staging

Plan: 1 to add, 0 to change, 1 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # 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-07-31T11:09:02Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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 #246

Copy link
Contributor

github-actions bot commented Jul 31, 2024

Terraform plan for production

Plan: 1 to add, 2 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+   create
!~  update in-place

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:ad305d45cd4b00de8cb2fcb91bc342b994adcbf6028de6f36efeaec3ca48247e" -> "ghcr.io/gsa-tts/fac/clamav@sha256:8df2e712eb361ca105f3f0b7655e50aef6f615eca013941a13bfc4f6bee7a1d9"
        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 will be created
+   resource "null_resource" "cors_header" {
+       id       = (known after apply)
+       triggers = {
+           "always_run" = (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:ad305d45cd4b00de8cb2fcb91bc342b994adcbf6028de6f36efeaec3ca48247e" -> "ghcr.io/gsa-tts/fac/clamav@sha256:8df2e712eb361ca105f3f0b7655e50aef6f615eca013941a13bfc4f6bee7a1d9"
        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, 0 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 applied in Deploy to Production Environment #95

Copy link
Contributor

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
18037 16481 91% 0% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 1bed165 by action🐍

@jadudm jadudm merged commit d9d3b2b into prod Jul 31, 2024
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autogenerated Automated pull request creation automerge Used for automated deployments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants