-
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
Remove SingleAuditChecklist._general_info_get()
#2444
Conversation
Terraform plan for meta No changes. Your infrastructure matches the configuration.
✅ Plan applied in Deploy to Development and Management Environment #274 |
Terraform plan for dev Plan: 0 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:
~ update in-place
Terraform will perform the following actions:
# module.dev.cloudfoundry_app.postgrest will be updated in-place
~ resource "cloudfoundry_app" "postgrest" {
~ docker_image = "ghcr.io/gsa-tts/fac/postgrest@sha256:5cb1228f3d1fc6f3d0151a99180d11b38488c9dd7a2eafd95e9e309d3c2fd9e8" -> "ghcr.io/gsa-tts/fac/postgrest@sha256:ded2f8ecea6853f73af1c679cdc6f9b8564978b9a028695bcce001b0a7f7fe3a"
id = "5de6f04c-52e0-400f-961a-16243b1c7c9a"
name = "postgrest"
# (15 unchanged attributes hidden)
# (1 unchanged block hidden)
}
# module.dev.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:8b88cea585056d4a67026a0fc5db8ba802a494ffae2a6959ddaceeb59e055a9b" -> "ghcr.io/gsa-tts/fac/clamav@sha256:080f8d91a5abe5e9069aac951bd02173394833bf763b2ed03eb31420f5c55db8"
id = "779bbc51-f78a-4186-90eb-5acb68d7d746"
name = "fac-av-dev"
# (15 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 2 to change, 0 to destroy.
Warning: Argument is deprecated
with module.dev.module.database.cloudfoundry_service_instance.rds,
on /tmp/terraform-data-dir/modules/dev.database/database/main.tf line 14, in resource "cloudfoundry_service_instance" "rds":
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 2 more similar warnings elsewhere) ✅ Plan applied in Deploy to Development and Management Environment #274 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 9d1b4f1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. This was my favorite method, BTW.
Methods can go stale.
We should remove those than have.
Even one-by-one.
We don't use this method anywhere that I can find.
No change is expected to the app; if the tests pass, this should be fine.
PR checklist: submitters
main
into your branch shortly before creating the PR. (You should also be mergingmain
into your branch regularly during development.)PR checklist: reviewers
make docker-clean; make docker-first-run && docker compose up
; then rundocker compose exec web /bin/bash -c "python manage.py test"
The larger the PR, the stricter we should be about these points.