fix: Add lifecycle to prevent changes when shared secret is updated #164
+4
−0
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
Add lifecycle to the VPN in order to prevent VPN replacement due to shared secrets being pulled by data resource from GCP Secrets Manager
<= data "google_secret_manager_secret_version" xxx" {
+ create_time = (known after apply)
+ destroy_time = (known after apply)
+ enabled = (known after apply)
+ id = (known after apply)
+ name = (known after apply)
+ secret_data = (sensitive value)
+ version = (known after apply)
}
-/+ resource "google_compute_vpn_tunnel" "tunnels" {
~ creation_timestamp = "2022-05-03T00:23:06.875-07:00" -> (known after apply)
~ detailed_status = "Tunnel is up and running." -> (known after apply)
~ label_fingerprint = "gYs4vEHLW2w=" -> (known after apply)
~ local_traffic_selector = [
- "0.0.0.0/0",
] -> (known after apply)
- peer_external_gateway_interface = 0 -> null
~ remote_traffic_selector = [
- "0.0.0.0/0",
] -> (known after apply)
~ shared_secret = (sensitive value) # forces replacement
}
imrannayer
changed the title
|
@ivayloivanov388 thx for the PR. Can you plz fix lint test? Follow this doc |
|
This PR is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add lifecycle to the VPN in order to prevent VPN replacement due to shared secrets being pulled by data resource from GCP Secrets Manager
<= data "google_secret_manager_secret_version" xxx" {
+ create_time = (known after apply)
+ destroy_time = (known after apply)
+ enabled = (known after apply)
+ id = (known after apply)
+ name = (known after apply)
+ secret_data = (sensitive value)
+ version = (known after apply)
}
-/+ resource "google_compute_vpn_tunnel" "tunnels" {
~ creation_timestamp = "2022-05-03T00:23:06.875-07:00" -> (known after apply)
~ detailed_status = "Tunnel is up and running." -> (known after apply)
~ label_fingerprint = "gYs4vEHLW2w=" -> (known after apply)
~ local_traffic_selector = [
- "0.0.0.0/0",
] -> (known after apply)
- peer_external_gateway_interface = 0 -> null
~ remote_traffic_selector = [
- "0.0.0.0/0",
] -> (known after apply)
~ shared_secret = (sensitive value) # forces replacement