-
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
2024-11-09 | MAIN --> PROD | DEV (24a933e) --> STAGING #4447
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
* Bootstrap module update * Meta provider update * Bootstrap-env template update * Preview local file regeneration * Dev local file regeneration * Fix preview provider * Fix dev provider * Fix shared env provider * Upgrade dev terraform lock * Upgrade preview lock * Change template * Full provider upgrade * fix glob issue on basename * Fix init.sh to prevent basename issues * Terraform Lock * Terraform Lock - Meta
* Fix preview provider * Fix dev provider * Change template * Full provider upgrade * Bump module versions to match upstream repo * CRLF -> LF * Remove depreciated recursive_delete * Missing stray deletion * terraform fmt
Terraform plan for staging Plan: 1 to add, 0 to change, 1 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# module.staging.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~ id = "*******************" -> (known after apply)
!~ triggers = { # forces replacement
!~ "always_run" = "2024-11-07T10:54:23Z" -> (known after apply)
}
}
Plan: 1 to add, 0 to change, 1 to destroy. ✅ Plan applied in Deploy to Staging Environment #289 |
Terraform plan for production Plan: 1 to add, 0 to change, 1 to destroy.Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# module.production.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~ id = "*******************" -> (known after apply)
!~ triggers = { # forces replacement
!~ "always_run" = "2024-11-06T18:55:28Z" -> (known after apply)
}
}
Plan: 1 to add, 0 to change, 1 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 📝 Plan generated in Pull Request Checks #3919 |
|
asteel-gsa
temporarily deployed
to
production
November 11, 2024 16:02 — with
GitHub Actions
Inactive
asteel-gsa
temporarily deployed
to
production
November 11, 2024 18:02 — with
GitHub Actions
Inactive
asteel-gsa
temporarily deployed
to
production
November 11, 2024 20:02 — with
GitHub Actions
Inactive
asteel-gsa
temporarily deployed
to
production
November 11, 2024 22:02 — with
GitHub Actions
Inactive
asteel-gsa
temporarily deployed
to
production
November 12, 2024 12:03 — with
GitHub Actions
Inactive
asteel-gsa
temporarily deployed
to
production
November 12, 2024 14:02 — with
GitHub Actions
Inactive
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 2024-11-09 with the last commit being merged as 24a933e