-
Notifications
You must be signed in to change notification settings - Fork 5
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-28 | MAIN --> PROD | DEV (6da1652) --> STAGING #2286
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
* Tribal Submission Schema * Tribal Submission Schema Test * Renamed TribalSubmission to TribalAcess * Modifications to match updates to ticket * Update backend/schemas/source/sections/TribalAccess.schema.jsonnet --------- Co-authored-by: Hassan D. M. Sambo <[email protected]>
* Fine tune queries, No dissemination of test data * Updates based on discussions * Updates based on discussions --------- Co-authored-by: Tadhg O'Higgins <[email protected]>
* Tribal Submission Schema * Tribal Submission Schema Test * Renamed TribalSubmission to TribalAcess * Modifications to match updates to ticket * Update backend/schemas/source/sections/TribalAccess.schema.jsonnet * #2209 Added logic to validate tribal data access * Fixed wrong test cases * #2209 Renamed fixture data file * Renamed test method --------- Co-authored-by: Sudha Kumar <[email protected]>
* FAC logo - new svg. Header - accordion darker text * Add filter to staticfiles directory * Add staticfiles section to development.md --------- Co-authored-by: Alex Steel <[email protected]>
Apparently, the headers are needed in order for them to show up. Should fix. Only way to test is to merge? No code files touched.
Co-authored-by: Matt Henry <[email protected]>
jadudm
added
autogenerated
Automated pull request creation
automerge
Used for automated deployments
labels
Sep 28, 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" {
id = "5e81ca8b-99cf-41f8-ae42-76652d51a44c"
name = "https-proxy"
~ source_code_hash = "48b2f5eba8d1f35c0fbc2f90c2ec87cab180f5f19e7e34b16b9190fe5c5ca09a" -> "9fcf4a7f6abfc9a220de2b8bb97591ab490a271ac0933b984f606f645319e1a4"
# (19 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 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 3 more similar warnings elsewhere) 📝 Plan generated in Pull Request Checks #1130 |
Terraform plan for staging 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.staging.module.https-proxy.cloudfoundry_app.egress_app will be updated in-place
~ resource "cloudfoundry_app" "egress_app" {
id = "1c9e7877-3c69-4fe5-8541-7bca3f845eb1"
name = "https-proxy"
~ source_code_hash = "48b2f5eba8d1f35c0fbc2f90c2ec87cab180f5f19e7e34b16b9190fe5c5ca09a" -> "9fcf4a7f6abfc9a220de2b8bb97591ab490a271ac0933b984f606f645319e1a4"
# (19 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Warning: Argument is deprecated
with module.staging.module.database.cloudfoundry_service_instance.rds,
on /tmp/terraform-data-dir/modules/staging.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 Staging Environment #53 |
Minimum allowed coverage is Generated by 🐒 cobertura-action against 6da1652 |
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-28 with the last commit being merged as 6da1652