-
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-09-02 | MAIN --> PROD | DEV (6138868) --> STAGING #2014
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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)
Ez/additional eins e2e
Update data loading as part of app deployment
Bump cf task instance allocations
jadudm
added
autogenerated
Automated pull request creation
automerge
Used for automated deployments
labels
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 |
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 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 6138868 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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