Fix k3s args

[github-actions[bot]]

Terraform Lint/Plan Results

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Plan 📖success

Terraform Validation 🤖success

Show Plan

``` terraform b2_bucket.terraform-state: Refreshing state... [id=c33185c9297d9b5484380d18] b2_bucket.tmeit-se-2011-dump: Refreshing state... [id=0351c5e9b99d1b0484480d18] b2_bucket.db-backups: Refreshing state... [id=531125b9d9ad0bd484480d18] tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4] tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3] tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d] hcloud_firewall.myfirewall: Refreshing state... [id=572118] cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149] cloudflare_record.mx-1: Refreshing state... [id=05ee2ea4ce180da1b784dfd3ade993c3] cloudflare_record.spf: Refreshing state... [id=93c69a0ddc2a7937bc30189d34a1e74f] data.cloudflare_api_token_permission_groups.all: Reading... data.cloudflare_api_token_permission_groups.all: Read complete after 0s [id=37f58c2e50041f9eed30c0006b111b44] hcloud_server.node1: Refreshing state... [id=25047988] b2_application_key.database-backup: Refreshing state... [id=00331599db448d80000000004] null_resource.run-ssh-install: Refreshing state... [id=5577006791947779410] hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62] hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1] cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88] cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46] cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d] cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a] cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5] 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: # b2_bucket.db-backups will be updated in-place ~ resource "b2_bucket" "db-backups" { id = "531125b9d9ad0bd484480d18" # (7 unchanged attributes hidden) ~ lifecycle_rules { ~ days_from_hiding_to_deleting = 365 -> 14 ~ file_name_prefix = "tmeit-db-backup-daily" -> "tmeit-db-backup-hourly" # (1 unchanged attribute hidden) } ~ lifecycle_rules { ~ days_from_hiding_to_deleting = 14 -> 365 ~ file_name_prefix = "tmeit-db-backup-hourly" -> "tmeit-db-backup-daily" # (1 unchanged attribute hidden) } # (2 unchanged blocks hidden) } # null_resource.run-ssh-install is tainted, so must be replaced -/+ resource "null_resource" "run-ssh-install" { ~ id = "5577006791947779410" -> (known after apply) ~ triggers = { ~ "always_run" = "2022-11-09T22:21:28Z" -> (known after apply) } } Plan: 1 to add, 1 to change, 1 to destroy. ───────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now. ```

Pushed by: @JustinLex, Action: pull_request