-
Notifications
You must be signed in to change notification settings - Fork 9
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
Terraform module updates #4692
base: main
Are you sure you want to change the base?
Terraform module updates #4692
Conversation
Terraform plan for dev Plan: 1 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 and then create replacement
Terraform will perform the following actions:
# module.dev.module.cors.null_resource.cors_header must be replaced
-/+ resource "null_resource" "cors_header" {
!~ id = "*******************" -> (known after apply)
!~ triggers = { # forces replacement
!~ "always_run" = "2025-02-11T17:04:54Z" -> (known after apply)
}
}
# module.dev.module.https-proxy.cloudfoundry_app.egress_app will be updated in-place
!~ resource "cloudfoundry_app" "egress_app" {
id = "a6eb3870-2769-4aa9-a8f2-f1a31939f563"
name = "https-proxy"
!~ source_code_hash = "9fcf4a7f6abfc9a220de2b8bb97591ab490a271ac0933b984f606f645319e1a4" -> "e246274fca627d48afccde010de949371f24b6c9974c48aa91044acd36654fa8"
# (21 unchanged attributes hidden)
# (1 unchanged block hidden)
}
Plan: 1 to add, 1 to change, 1 to destroy. 📝 Plan generated in Pull Request Checks #4369 |
Terraform plan for meta No changes. Your infrastructure matches the configuration.
📝 Plan generated in Pull Request Checks #4369 |
This pull request is not up to date with main. Please merge main into this brach or rebase this branch onto main. This PR should not be approved until all status checks pass. If you see this message, please rerun all status checks before merging. |
This pull request is not up to date with main. Please merge main into this brach or rebase this branch onto main. This PR should not be approved until all status checks pass. If you see this message, please rerun all status checks before merging. |
This pull request is not up to date with main. Please merge main into this brach or rebase this branch onto main. This PR should not be approved until all status checks pass. If you see this message, please rerun all status checks before merging. |
Sets the new provider into the terraform providers.tf and runs a dual provider setup, forcing any resource that does not natively interact with the new provider using: provider = cloudfoundry-community
- Removes app_name_or_id for network policies - Reintroduces external network policy for clamav -> proxy - Deployed successfully around 9a with v2.0.0 clamav module and was able to successfully validate a file at around 916a without any issues
a1c45aa
to
98d01ab
Compare
|
This PR encapsulates the necessary changes to upgrade our modules from
v1.1.0
tov2.1.0
insandbox
. The process is detailed in the new docdocs/infra/terraform-module-upgrade.md
This will require 1-2 members of the team to do a call and walkthrough exactly what is happening behind the scenes. Once we move this into
main
, we will need to repeat these steps inpreview
on a call and ensure everything works the same way. Because we have toimport
the resource, I believe each environment will need changes to themain.tf
file, and it is recommended that we proceed carefully.My hunch at this time, is to perform these steps locally, run the apply locally, and then open a PR to keep things in sync.
For the new network policy for
app -> clamav
, I believe we will need to add this into the terraform for non-sandbox envs: