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

2023-09-02 | MAIN --> PROD | DEV (6138868) --> STAGING #2014

Merged
merged 20 commits into from
Sep 2, 2023
Merged

2023-09-02 | MAIN --> PROD | DEV (6138868) --> STAGING #2014

merged 20 commits into from
Sep 2, 2023

Conversation

jadudm
Copy link
Contributor

@jadudm jadudm commented Sep 2, 2023

This is an auto-generated pull request to merge main into prod for a staging release on 2023-09-02 with the last commit being merged as 6138868

Edward Zapata and others added 20 commits August 31, 2023 15:04
Not needed - invoke via bin/ops and call the wait-and-load.sh as
part of the app deployment.
This is a requirement so that we can get psql to run the data loading script
We need to be able to pull down the data loading repo.

NOTE: we need to scope down *.github to be the redirect url for git's
hosting service in a subsequent PR.
This script will grab the historical data, and then execute it as part
of our app deployments.
If we don't do this, then the default Ubuntu pg_wrapper script will be
called, and it gets very confused because it's not written to be
location-independent.
This will allow us to call wait-and-load as normal.
(This is seperating it out from the dockerfile)
Update data loading as part of app deployment
Bump cf task instance allocations
@jadudm jadudm added autogenerated Automated pull request creation automerge Used for automated deployments labels Sep 2, 2023
@jadudm jadudm temporarily deployed to production September 2, 2023 10:34 — with GitHub Actions Inactive
@jadudm jadudm temporarily deployed to staging September 2, 2023 10:34 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2023

Terraform plan for production

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

Terraform will perform the following actions:

  # module.production.module.https-proxy.cloudfoundry_app.egress_app will be updated in-place
  ~ resource "cloudfoundry_app" "egress_app" {
      ~ environment                     = (sensitive value)
        id                              = "5e81ca8b-99cf-41f8-ae42-76652d51a44c"
      ~ id_bg                           = "************************************" -> (known after apply)
        name                            = "https-proxy"
        # (17 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

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

📝 Plan generated in Pull Request Checks #788

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2023

Terraform plan for staging

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

Terraform will perform the following actions:

  # module.staging.cloudfoundry_app.data_load will be destroyed
  # (because cloudfoundry_app.data_load is not in configuration)
  - resource "cloudfoundry_app" "data_load" {
      - disk_quota                      = 64 -> null
      - docker_image                    = "ghcr.io/gsa-tts/fac-historic-public-csvs/load-historic-public-data@sha256:8b6c2b1110e37de2bb0e4e38e3ab9b612118b0365d7f008c5ec8466aa149fea6" -> null
      - enable_ssh                      = true -> null
      - environment                     = (sensitive value) -> null
      - health_check_invocation_timeout = 0 -> null
      - health_check_timeout            = 0 -> null
      - health_check_type               = "port" -> null
      - id                              = "fb5edd1e-5287-4db0-befa-5e05bf676418" -> null
      - id_bg                           = "fb5edd1e-5287-4db0-befa-5e05bf676418" -> null
      - instances                       = 1 -> null
      - memory                          = 64 -> null
      - name                            = "dataload" -> null
      - ports                           = [] -> null
      - space                           = "7bbe587a-e8ee-4e8c-b32f-86d0b0f1b807" -> null
      - stopped                         = false -> null
      - strategy                        = "rolling" -> null
      - timeout                         = 180 -> null
    }

  # module.staging.module.https-proxy.cloudfoundry_app.egress_app will be updated in-place
  ~ resource "cloudfoundry_app" "egress_app" {
      ~ environment                     = (sensitive value)
        id                              = "1c9e7877-3c69-4fe5-8541-7bca3f845eb1"
      ~ id_bg                           = "************************************" -> (known after apply)
        name                            = "https-proxy"
        # (17 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

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

✅ Plan applied in Deploy to Staging Environment #32

@github-actions
Copy link
Contributor

github-actions bot commented Sep 2, 2023

File Coverage Missing
All files 88%
api/serializers.py 89% 121-122 127 132
api/test_views.py 99%
api/uei.py 96% 17-18 107-108
api/views.py 97% 197-198 205-206 227 405-406
audit/cog_agency.py 94% 49
audit/cog_over.py 53% 73-116 120-136 144
audit/etl.py 78% 55-56 73-74 107 194-200 214-235 256 271 401-430
audit/excel.py 87% 397 413 419 424 429 451-452 464 665-666 675-681 691 711
audit/forms.py 56% 22-29
audit/models.py 86% 101 179 335 353-354 362 384 441-444 473-474 478 486 495 505 508-514
audit/test_commands.py 87%
audit/test_etl.py 97% 235-250 331-334
audit/test_mixins.py 90% 112-113 117-119 184-185 189-191
audit/test_validators.py 95% 434 438 606-607 846 853 860 867
audit/utils.py 92% 12
audit/validators.py 96% 253-254 282-283 298-299 309 500-509
audit/views.py 37% 86-107 130-131 205-206 251-252 262-273 317-330 333-347 352-365 382-388 393-413 440-444 449-478 521-525 530-550 577-581 586-615 658-662 667-679 682-693 698-710 725-726 731-780 783-823 826-843
audit/cross_validation/additional_ueis.py 93% 33
audit/cross_validation/check_award_ref_declaration.py 90%
audit/cross_validation/check_award_reference_uniqueness.py 93%
audit/cross_validation/check_findings_count_consistency.py 91%
audit/cross_validation/check_ref_number_in_cap.py 90%
audit/cross_validation/check_ref_number_in_findings_text.py 90%
audit/cross_validation/errors.py 78% 30 61
audit/cross_validation/naming.py 68% 178-182
audit/cross_validation/submission_progress_check.py 82% 62 77-80
audit/cross_validation/tribal_data_sharing_consent.py 86% 20
audit/fixtures/single_audit_checklist.py 79% 155 231-240
audit/management/commands/load_fixtures.py 46% 39-45
audit/viewlib/submission_progress_view.py 96% 158-159
audit/viewlib/upload_report_view.py 30% 32-35 44 91-115 118-186
cms/views.py 57% 11-16 29-30
config/urls.py 71% 87
dissemination/models.py 99% 685
djangooidc/backends.py 78% 32 57-63
djangooidc/exceptions.py 66% 19 21 23 28
djangooidc/oidc.py 15% 32-35 45-51 64-70 78-84 92-149 153-199 203-226 230-275 280-281
djangooidc/views.py 78% 23-26 43 114
djangooidc/tests/common.py 96%
report_submission/forms.py 90% 9
report_submission/views.py 72% 82 195-197 199 205-312 315-325
report_submission/templatetags/get_attr.py 76% 8 11-14 18
tools/update_program_data.py 89% 96
users/auth.py 95% 39-40
users/fixtures/user_fixtures.py 91%

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against 6138868

@jadudm jadudm merged commit 15dfe20 into prod Sep 2, 2023
41 checks passed
@asteel-gsa asteel-gsa temporarily deployed to staging September 4, 2023 09:01 — with GitHub Actions Inactive
@asteel-gsa asteel-gsa temporarily deployed to staging September 5, 2023 09:01 — with GitHub Actions Inactive
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.

4 participants