-
Notifications
You must be signed in to change notification settings - Fork 7
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-08-26 | MAIN --> PROD | DEV (aa9b1d5) --> STAGING #1955
Conversation
Change language for threshold on audit info form
Error Pages
Closes #1585 In this PR: Adding logout command Tweaking login command so that you can optionally specify credentials Cypress test now logs out, then logs in with an auditee account, who then performs the auditee cert Testing: Cypress tests should pass New env vars required: LOGIN_TEST_EMAIL_AUDITEE, LOGIN_TEST_PASSWORD_AUDITEE, LOGIN_TEST_OTP_SECRET_AUDITEE This email will be used for the auditee info form and will be used to perform the auditee cert You can use values from the FAC dev keys doc These have been added to the GH staging env vars as well --------- Co-authored-by: Phil Dominguez <“philip.dominguez@gsa.gov”> Co-authored-by: Edward Zapata <edward.zapata@gsa.gov>
* Move SubmissionProgressView into its own file ahead of work on it. * Update/refactor submission_progress_check to return new requirements, and change tests accordingly. + Change the logic for Submission progress to display complete/incomplete/inactive. + Change the logic for Submission progress to treat findings/findings text/corrective action plan as optional instead of always required. + Switch submission-checklist.html to using section_block for each section. + Switch audit/report-submission/CAP/ to audit/report-submission/cap hopefully everywhere. + Move some functions that were in sac_validation_shape.py to naming.py. * Minor corrections. --------- Co-authored-by: Edward Zapata <edward.zapata@gsa.gov>
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Terraform plan for staging No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Staging Environment #26 |
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.cloudfoundry_app.postgrest will be updated in-place
~ resource "cloudfoundry_app" "postgrest" {
~ environment = (sensitive value)
id = "70ac44be-3507-4867-a75f-c2d1ab12ee89"
~ id_bg = "************************************" -> (known after apply)
~ memory = 128 -> 512
name = "postgrest"
# (12 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy. 📝 Plan generated in Pull Request Checks #718 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against aa9b1d5 |
This is an auto-generated pull request to merge main into prod for a staging release on 2023-08-26 with the last commit being merged as aa9b1d5