Skip to content
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

Password reset function #221

Merged
merged 30 commits into from
Feb 5, 2024
Merged

Password reset function #221

merged 30 commits into from
Feb 5, 2024

Conversation

JustinLex
Copy link
Member

No description provided.

f'Hi {full_name},\n\n'
'You are receiving this email since a pasword reset has been requested for your tmeit account.\n\n'
'If you did not make this request, please ignore this message.\n\n'
f'You can reset your password by visiting <a href=\"localhost:8080/reset/{reset_token}\" target="_blank" rel="noreferrer noopener">tmeit.se/reset/{reset_token}</a>\n\n'
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

href should be changed to tmeit.se. Maybe we should add a environment variable for the current server URL, so that this works for both dev and prod.

email : email
};

const xhr = new XMLHttpRequest();
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


const address = "/api/v1/reset/" + reset_token + "?email=" + email;

const xhr = new XMLHttpRequest();
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wretch here too?

…pes in comparisons, but it's somehow like records are never added to the database...
Copy link

github-actions bot commented Feb 1, 2024

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]
tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d]
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
data.cloudflare_api_token_permission_groups.all: Reading...
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]
cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149]
hcloud_firewall.myfirewall: Refreshing state... [id=572118]
data.cloudflare_api_token_permission_groups.all: Read complete after 0s [id=faeb3cfa42819bea22595530c2cf9f01]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
hcloud_server.node1: Refreshing state... [id=25047988]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1]
hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62]
cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5]
cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a]
cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]
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:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

…e it was set up so that only one transaction could be performed - the only one which was used up for looking up the uuid corresponding to the mail address. This has now been fixed
Copy link

github-actions bot commented Feb 3, 2024

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]
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
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]
tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d]
tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3]
tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
data.cloudflare_api_token_permission_groups.all: Read complete after 1s [id=faeb3cfa42819bea22595530c2cf9f01]
hcloud_server.node1: Refreshing state... [id=25047988]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d]
cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5]
cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
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]
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:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

Copy link

github-actions bot commented Feb 3, 2024

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.db-backups: Refreshing state... [id=531125b9d9ad0bd484480d18]
b2_bucket.tmeit-se-2011-dump: Refreshing state... [id=0351c5e9b99d1b0484480d18]
hcloud_firewall.myfirewall: Refreshing state... [id=572118]
tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d]
tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4]
tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3]
data.cloudflare_api_token_permission_groups.all: Reading...
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149]
data.cloudflare_api_token_permission_groups.all: Read complete after 1s [id=faeb3cfa42819bea22595530c2cf9f01]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
hcloud_server.node1: Refreshing state... [id=25047988]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a]
cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1]
cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5]
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:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

Copy link

github-actions bot commented Feb 4, 2024

Terraform Lint/Plan Results

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Plan 📖success

Terraform Validation 🤖success

Show Plan

terraform
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
data.cloudflare_api_token_permission_groups.all: Reading...
tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d]
tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4]
tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3]
b2_bucket.terraform-state: Refreshing state... [id=c33185c9297d9b5484380d18]
cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149]
b2_bucket.tmeit-se-2011-dump: Refreshing state... [id=0351c5e9b99d1b0484480d18]
b2_bucket.db-backups: Refreshing state... [id=531125b9d9ad0bd484480d18]
hcloud_firewall.myfirewall: Refreshing state... [id=572118]
data.cloudflare_api_token_permission_groups.all: Read complete after 1s [id=faeb3cfa42819bea22595530c2cf9f01]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
b2_application_key.database-backup: Refreshing state... [id=00331599db448d80000000004]
hcloud_server.node1: Refreshing state... [id=25047988]
hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1]
cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a]
cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

Copy link

github-actions bot commented Feb 4, 2024

Terraform Lint/Plan Results

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Plan 📖success

Terraform Validation 🤖success

Show Plan

terraform
data.cloudflare_api_token_permission_groups.all: Reading...
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
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]
tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3]
tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4]
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]
data.cloudflare_api_token_permission_groups.all: Read complete after 0s [id=faeb3cfa42819bea22595530c2cf9f01]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
hcloud_server.node1: Refreshing state... [id=25047988]
cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]
cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5]
hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62]
cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1]
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:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

Copy link

github-actions bot commented Feb 5, 2024

Terraform Lint/Plan Results

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Plan 📖success

Terraform Validation 🤖success

Show Plan

terraform
data.cloudflare_api_token_permission_groups.all: Reading...
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
b2_bucket.terraform-state: Refreshing state... [id=c33185c9297d9b5484380d18]
tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3]
b2_bucket.db-backups: Refreshing state... [id=531125b9d9ad0bd484480d18]
tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4]
cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149]
b2_bucket.tmeit-se-2011-dump: Refreshing state... [id=0351c5e9b99d1b0484480d18]
hcloud_firewall.myfirewall: Refreshing state... [id=572118]
tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d]
data.cloudflare_api_token_permission_groups.all: Read complete after 1s [id=faeb3cfa42819bea22595530c2cf9f01]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
hcloud_server.node1: Refreshing state... [id=25047988]
b2_application_key.database-backup: Refreshing state... [id=00331599db448d80000000004]
hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
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]
hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62]

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

Copy link

github-actions bot commented Feb 5, 2024

Terraform Lint/Plan Results

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Plan 📖success

Terraform Validation 🤖success

Show Plan

terraform
data.cloudflare_api_token_permission_groups.all: Reading...
tls_private_key.dkim-rsa: Refreshing state... [id=1b2806ad50f04aac1c2d9b7ce7ba47f00ed31eb4]
tls_private_key.terraform_access: Refreshing state... [id=2ffac8d1a1e85232461425b441d27bce00a220c3]
hcloud_firewall.myfirewall: Refreshing state... [id=572118]
tls_private_key.dkim-ed25519: Refreshing state... [id=68fff8299fe24966516127ec74f88c48a9825a3d]
cloudflare_record.spf-website: Refreshing state... [id=6996f2e9fb76eded73fa32bde6a4910f]
cloudflare_zone_settings_override.tmeit-se-settings: Refreshing state... [id=6a806c0199e15cdf23bb3017a90bf149]
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]
data.cloudflare_api_token_permission_groups.all: Read complete after 0s [id=faeb3cfa42819bea22595530c2cf9f01]
hcloud_server.node1: Refreshing state... [id=25047988]
cloudflare_record.spf: Refreshing state... [id=4d62468769e45285f7bff8f779a3608c]
hcloud_rdns.node1_ipv4: Refreshing state... [id=s-25047988-65.21.188.62]
cloudflare_record.node1-aaaa: Refreshing state... [id=2204e4ec36dbcc3a1e01f6799279a2f5]
cloudflare_record.node1-a: Refreshing state... [id=9ef92757893c62ea5d1f59037eb0012a]
cloudflare_api_token.dns_validation_token: Refreshing state... [id=c8a740fd710299e7612975c93125667d]
null_resource.run-ssh-install: Refreshing state... [id=7623419525618991727]
cloudflare_record.www-aaaa: Refreshing state... [id=9f7b0d63a18b5513abb8db23ce62cd46]
hcloud_rdns.node1_ipv6: Refreshing state... [id=s-25047988-2a01:4f9:c012:6063::1]
cloudflare_record.root-aaaa: Refreshing state... [id=d357e52c5cacabec46933fa577fb0e88]
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:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # null_resource.run-ssh-install must be replaced
-/+ resource "null_resource" "run-ssh-install" {
      ~ id       = "7623419525618991727" -> (known after apply)
      ~ triggers = { # forces replacement
          ~ "always_run" = "2024-02-01T06:31:05Z" -> (known after apply)
        }
    }

Plan: 1 to add, 0 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

@Sebbedi Sebbedi merged commit a38b726 into master Feb 5, 2024
8 checks passed
@Sebbedi Sebbedi deleted the password_reset_function branch February 5, 2024 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants