Fixed frontend part of new prao approvals not being sent to API - also made the approve signups-view look nicer

Terraform Lint/Plan Results

Terraform Format and Style 🖌`success`

Terraform Initialization ⚙️`success`

Terraform Plan 📖`success`

Terraform Validation 🤖`success`

Show Plan

``` terraform tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d] b2_bucket.tmeit-se-2011-dump: Refreshing state... [id=0351c5e9b99d1b0484480d18] tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3] b2_bucket.db-backups: Refreshing state... [id=531125b9d9ad0bd484480d18] b2_bucket.terraform-state: Refreshing state... [id=c33185c9297d9b5484380d18] tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4] hcloud_firewall.myfirewall: Refreshing state... [id=572118] data.cloudflare_api_token_permission_groups.all: Reading... cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149] cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c] data.cloudflare_api_token_permission_groups.all: Read complete after 1s [id=a165ae77435ca2ae08f741a49c8544f2] hcloud_server.node1: Refreshing state... [id=25047988] hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1] cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46] cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a] cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5] cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d] cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88] null_resource.run-ssh-install: Refreshing state... [id=5186499270613435001] hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62] b2_application_key.database-backup: Refreshing state... [id=00331599db448d80000000004] Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create ~ update in-place -/+ destroy and then create replacement Terraform will perform the following actions: # cloudflare_record.spf will be updated in-place ~ resource "cloudflare_record" "spf" { id = "4d62468769e45285f7bff8f779a3608c" name = "@" ~ value = "v=spf1 +mx -all" -> (known after apply) # (10 unchanged attributes hidden) } # cloudflare_record.spf-website will be created + resource "cloudflare_record" "spf-website" { + 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 = "node1" + proxiable = (known after apply) + proxied = false + ttl = (known after apply) + type = "TXT" + value = "v=spf1 a -all" + zone_id = "6a806c0199e15cdf23bb3017a90bf149" } # null_resource.run-ssh-install must be replaced -/+ resource "null_resource" "run-ssh-install" { ~ id = "5186499270613435001" -> (known after apply) ~ triggers = { # forces replacement ~ "always_run" = "2023-07-04T21:50:30Z" -> (known after apply) } } Plan: 2 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: @Sebbedi, Action: pull_request

TMEIT / website