cache dns changes for azure functions #83
Closed
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
👋 Thanks for opening a pull request!If you are new, please check out the deployment process to understand how to deploy this pull request. A trimmed down summary will be listed below:
|
|
.noop |
Deployment Triggered 🚀GrantBirki, started a noop deployment to production You can watch the progress here 🔗
|
Deployment Results ✅GrantBirki successfully noop deployed branch Show ResultsNote: Objects have changed outside of Terraform
Terraform detected the following changes made outside of Terraform since the
last "terraform apply":
# cloudflare_record.cache has changed
~ resource "cloudflare_record" "cache" {
id = "03fe31c72264d5c29ed63ab520988055"
~ modified_on = "2023-01-03T03:52:24.455009Z" -> "2024-03-10T23:24:25.455763Z"
name = "cache"
# (10 unchanged attributes hidden)
}
Unless you have made equivalent changes to your configuration, or ignored the
relevant attributes using ignore_changes, the following plan may include
actions to undo or respond to these changes.
─────────────────────────────────────────────────────────────────────────────
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
~ update in-place
Terraform will perform the following actions:
# cloudflare_record.cache will be updated in-place
~ resource "cloudflare_record" "cache" {
id = "03fe31c72264d5c29ed63ab520988055"
name = "cache"
~ value = "20.124.115.39" -> "20.49.104.36"
# (10 unchanged attributes hidden)
}
# cloudflare_record.cache_azure_function_verification will be created
+ resource "cloudflare_record" "cache_azure_function_verification" {
+ allow_overwrite = false
+ created_on = (known after apply)
+ hostname = (known after apply)
+ id = (known after apply)
+ metadata = (known after apply)
+ modified_on = (known after apply)
+ name = "asuid.cache"
+ proxiable = (known after apply)
+ ttl = 1
+ type = "TXT"
+ value = "966A35FCB4A0FE1176E2320038F9EA960F6E2FE36A69ABDFC79A272FE4E2228F"
+ zone_id = "a17204c79af55fcf05e4975f66e2490e"
}
Plan: 1 to add, 1 to change, 0 to destroy.
|
|
.deploy |
Deployment Triggered 🚀GrantBirki, started a branch deployment to production You can watch the progress here 🔗
|
Deployment Results ✅GrantBirki successfully branch deployed branch Show ResultsNote: Objects have changed outside of Terraform
Terraform detected the following changes made outside of Terraform since the
last "terraform apply":
# cloudflare_record.cache has changed
~ resource "cloudflare_record" "cache" {
id = "03fe31c72264d5c29ed63ab520988055"
~ modified_on = "2023-01-03T03:52:24.455009Z" -> "2024-03-10T23:24:25.455763Z"
name = "cache"
# (10 unchanged attributes hidden)
}
Unless you have made equivalent changes to your configuration, or ignored the
relevant attributes using ignore_changes, the following plan may include
actions to undo or respond to these changes.
─────────────────────────────────────────────────────────────────────────────
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
~ update in-place
Terraform will perform the following actions:
# cloudflare_record.cache will be updated in-place
~ resource "cloudflare_record" "cache" {
id = "03fe31c72264d5c29ed63ab520988055"
name = "cache"
~ value = "20.124.115.39" -> "20.49.104.36"
# (10 unchanged attributes hidden)
}
# cloudflare_record.cache_azure_function_verification will be created
+ resource "cloudflare_record" "cache_azure_function_verification" {
+ allow_overwrite = false
+ created_on = (known after apply)
+ hostname = (known after apply)
+ id = (known after apply)
+ metadata = (known after apply)
+ modified_on = (known after apply)
+ name = "asuid.cache"
+ proxiable = (known after apply)
+ ttl = 1
+ type = "TXT"
+ value = "966A35FCB4A0FE1176E2320038F9EA960F6E2FE36A69ABDFC79A272FE4E2228F"
+ zone_id = "a17204c79af55fcf05e4975f66e2490e"
}
Plan: 1 to add, 1 to change, 0 to destroy.
cloudflare_record.cache_azure_function_verification: Creating...
cloudflare_record.cache: Modifying... [id=03fe31c72264d5c29ed63ab520988055]
cloudflare_record.cache_azure_function_verification: Creation complete after 1s [id=b578015ae49681c40dc6569437be6158]
cloudflare_record.cache: Modifications complete after 2s [id=03fe31c72264d5c29ed63ab520988055]
Apply complete! Resources: 1 added, 1 changed, 0 destroyed.
|
|
.deploy main |
Deployment Triggered 🚀GrantBirki, started a branch deployment to production You can watch the progress here 🔗
|
Deployment Results ✅GrantBirki successfully branch deployed branch Show ResultsTerraform 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:
# cloudflare_record.cache will be updated in-place
~ resource "cloudflare_record" "cache" {
id = "03fe31c72264d5c29ed63ab520988055"
name = "cache"
~ value = "20.49.104.36" -> "20.124.115.39"
# (10 unchanged attributes hidden)
}
# cloudflare_record.cache_azure_function_verification will be destroyed
# (because cloudflare_record.cache_azure_function_verification is not in configuration)
- resource "cloudflare_record" "cache_azure_function_verification" {
- allow_overwrite = false -> null
- created_on = "2024-03-10T23:32:30.377657Z" -> null
- hostname = "asuid.cache.tarkov.dev" -> null
- id = "b578015ae49681c40dc6569437be6158" -> null
- metadata = {
- "auto_added" = "false"
- "managed_by_apps" = "false"
- "managed_by_argo_tunnel" = "false"
} -> null
- modified_on = "2024-03-10T23:32:30.377657Z" -> null
- name = "asuid.cache" -> null
- proxiable = false -> null
- proxied = false -> null
- ttl = 1 -> null
- type = "TXT" -> null
- value = "966A35FCB4A0FE1176E2320038F9EA960F6E2FE36A69ABDFC79A272FE4E2228F" -> null
- zone_id = "a17204c79af55fcf05e4975f66e2490e" -> null
}
Plan: 0 to add, 1 to change, 1 to destroy.
cloudflare_record.cache_azure_function_verification: Destroying... [id=b578015ae49681c40dc6569437be6158]
cloudflare_record.cache: Modifying... [id=03fe31c72264d5c29ed63ab520988055]
cloudflare_record.cache_azure_function_verification: Destruction complete after 0s
cloudflare_record.cache: Modifications complete after 1s [id=03fe31c72264d5c29ed63ab520988055]
Apply complete! Resources: 0 added, 1 changed, 1 destroyed.
|
|
.deploy |
Deployment Triggered 🚀GrantBirki, started a branch deployment to production You can watch the progress here 🔗
|
Deployment Results ✅GrantBirki successfully branch deployed branch Show ResultsTerraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
-/+ destroy and then create replacement
Terraform will perform the following actions:
# cloudflare_record.cache must be replaced
-/+ resource "cloudflare_record" "cache" {
~ created_on = "2022-06-11T16:27:09.021018Z" -> (known after apply)
~ hostname = "cache.tarkov.dev" -> (known after apply)
~ id = "03fe31c72264d5c29ed63ab520988055" -> (known after apply)
~ metadata = {
- "auto_added" = "false"
- "managed_by_apps" = "false"
- "managed_by_argo_tunnel" = "false"
} -> (known after apply)
~ modified_on = "2024-03-10T23:34:38.311464Z" -> (known after apply)
name = "cache"
~ proxiable = true -> (known after apply)
~ type = "A" -> "CNAME" # forces replacement
~ value = "20.124.115.39" -> "tarkov-cache.azurewebsites.net"
# (4 unchanged attributes hidden)
}
# cloudflare_record.cache_azure_function_verification will be created
+ resource "cloudflare_record" "cache_azure_function_verification" {
+ allow_overwrite = false
+ created_on = (known after apply)
+ hostname = (known after apply)
+ id = (known after apply)
+ metadata = (known after apply)
+ modified_on = (known after apply)
+ name = "asuid.cache"
+ proxiable = (known after apply)
+ ttl = 1
+ type = "TXT"
+ value = "966A35FCB4A0FE1176E2320038F9EA960F6E2FE36A69ABDFC79A272FE4E2228F"
+ zone_id = "a17204c79af55fcf05e4975f66e2490e"
}
Plan: 2 to add, 0 to change, 1 to destroy.
cloudflare_record.cache: Destroying... [id=03fe31c72264d5c29ed63ab520988055]
cloudflare_record.cache_azure_function_verification: Creating...
cloudflare_record.cache: Destruction complete after 0s
cloudflare_record.cache: Creating...
cloudflare_record.cache_azure_function_verification: Creation complete after 1s [id=2f52f776bbb5d137730086c7579663a4]
cloudflare_record.cache: Creation complete after 1s [id=180e6c5a5414843333d449244962bf01]
Apply complete! Resources: 2 added, 0 changed, 1 destroyed.
|
|
.deploy main |
Deployment Triggered 🚀GrantBirki, started a branch deployment to production You can watch the progress here 🔗
|
Deployment Results ✅GrantBirki successfully branch deployed branch Show ResultsNote: Objects have changed outside of Terraform
Terraform detected the following changes made outside of Terraform since the
last "terraform apply":
# cloudflare_record.cache has changed
~ resource "cloudflare_record" "cache" {
id = "180e6c5a5414843333d449244962bf01"
~ modified_on = "2024-03-10T23:38:24.520299Z" -> "2024-03-10T23:48:48.384528Z"
name = "cache"
# (10 unchanged attributes hidden)
}
Unless you have made equivalent changes to your configuration, or ignored the
relevant attributes using ignore_changes, the following plan may include
actions to undo or respond to these changes.
─────────────────────────────────────────────────────────────────────────────
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
- destroy
-/+ destroy and then create replacement
Terraform will perform the following actions:
# cloudflare_record.cache must be replaced
-/+ resource "cloudflare_record" "cache" {
~ created_on = "2024-03-10T23:38:24.520299Z" -> (known after apply)
~ hostname = "cache.tarkov.dev" -> (known after apply)
~ id = "180e6c5a5414843333d449244962bf01" -> (known after apply)
~ metadata = {
- "auto_added" = "false"
- "managed_by_apps" = "false"
- "managed_by_argo_tunnel" = "false"
} -> (known after apply)
~ modified_on = "2024-03-10T23:48:48.384528Z" -> (known after apply)
name = "cache"
~ proxiable = true -> (known after apply)
~ type = "CNAME" -> "A" # forces replacement
~ value = "tarkov-cache.azurewebsites.net" -> "20.124.115.39"
# (4 unchanged attributes hidden)
}
# cloudflare_record.cache_azure_function_verification will be destroyed
# (because cloudflare_record.cache_azure_function_verification is not in configuration)
- resource "cloudflare_record" "cache_azure_function_verification" {
- allow_overwrite = false -> null
- created_on = "2024-03-10T23:38:24.26144Z" -> null
- hostname = "asuid.cache.tarkov.dev" -> null
- id = "2f52f776bbb5d137730086c7579663a4" -> null
- metadata = {
- "auto_added" = "false"
- "managed_by_apps" = "false"
- "managed_by_argo_tunnel" = "false"
} -> null
- modified_on = "2024-03-10T23:38:24.26144Z" -> null
- name = "asuid.cache" -> null
- proxiable = false -> null
- proxied = false -> null
- ttl = 1 -> null
- type = "TXT" -> null
- value = "966A35FCB4A0FE1176E2320038F9EA960F6E2FE36A69ABDFC79A272FE4E2228F" -> null
- zone_id = "a17204c79af55fcf05e4975f66e2490e" -> null
}
Plan: 1 to add, 0 to change, 2 to destroy.
cloudflare_record.cache: Destroying... [id=180e6c5a5414843333d449244962bf01]
cloudflare_record.cache_azure_function_verification: Destroying... [id=2f52f776bbb5d137730086c7579663a4]
cloudflare_record.cache: Destruction complete after 0s
cloudflare_record.cache: Creating...
cloudflare_record.cache_azure_function_verification: Destruction complete after 0s
cloudflare_record.cache: Creation complete after 1s [id=65105596207eb686b256c9bb9cd17e23]
Apply complete! Resources: 1 added, 0 changed, 2 destroyed.
|
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.
No description provided.