Pritunl2

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

atlantis plan

Ran Plan for dir: terraform/atlantis workspace: default
Plan Error
Show Output
running "/usr/local/bin/terraform init -input=false -no-color -upgrade" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis": exit status 1
There are some problems with the configuration, described below.

The Terraform configuration must be valid before initialization so that
Terraform can determine which modules and providers need to be installed.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Error: Duplicate data "digitalocean_kubernetes_cluster" configuration

  on k8s.tf line 1:
   1: data "digitalocean_kubernetes_cluster" "k8s" {

A digitalocean_kubernetes_cluster data resource named "k8s" was already
declared at data.tf:5,1-45. Resource names must be unique per type in each
module.

Error: Duplicate provider configuration

  on k8s.tf line 5:
   5: provider "kubernetes" {

A default (non-aliased) provider configuration for "kubernetes" was already
given at data.tf:9,1-22. If multiple configurations are required, set the
"alias" argument for alternative configurations.

Error: Duplicate provider configuration

  on k8s.tf line 13:
  13: provider "helm" {

A default (non-aliased) provider configuration for "helm" was already given
at data.tf:17,1-16. If multiple configurations are required, set the "alias"
argument for alternative configurations.

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14762570" -> "14765735"
            # (4 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:
~ update in-place
- destroy
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # helm_release.mongodb must be replaced
-/+ resource "helm_release" "mongodb" {
      ~ id                         = "pritunl-mongodb" -> (known after apply)
      + manifest                   = (known after apply)
      ~ metadata                   = [
          - {
              - app_version = "4.4.13"
              - chart       = "mongodb"
              - name        = "pritunl-mongodb"
              - namespace   = "pritunl"
              - revision    = 2
              - values      = jsonencode(
                    {
                      - auth = {
                          - database     = "pritunl"
                          - password     = "IJfedsdaHHffhd323a"
                          - rootPassword = "IJfedsdaHHffhd323a"
                          - rootUser     = "admin"
                          - username     = "admin"
                        }
                    }
                )
              - version     = "11.1.2"
            },
        ] -> (known after apply)
      ~ name                       = "pritunl-mongodb" -> "mongodb" # forces replacement
      ~ namespace                  = "pritunl" -> "mongodb" # forces replacement
      ~ repository                 = "./helm_charts" -> "https://charts.bitnami.com/bitnami"
      - values                     = [
          - (sensitive),
        ] -> null
      ~ version                    = "11.1.2" -> "11.0.6"
        # (22 unchanged attributes hidden)
    }

  # helm_release.pritunl will be updated in-place
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ values                     = [
          - <<-EOT
                image:
                  registry: ghcr.io
                  repository: autotune/pritunl-k8s-tf-do/autotune/pritunl-k8s-tf-do
                  tag: pritunl:dc7700e4
                  pullPolicy: Always
                  pullSecret: "wayofthesys-com-docker-login"
                  domain_name: "wayofthesys-com"

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 80

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
          + <<-EOT
                image:
                  registry: docker.pkg.github.com
                  repository: autotune/pritunl-k8s-tf-do
                  tag: latest
                  pullPolicy: Always

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 443

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
        ]
      ~ version                    = "0.0.8" -> "0.0.1"
        # (25 unchanged attributes hidden)
    }

  # kubernetes_secret.docker_login_secret will be destroyed
- resource "kubernetes_secret" "docker_login_secret" {
      - data      = (sensitive value)
      - id        = "pritunl/wayofthesys-com-docker-login" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/dockerconfigjson" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "wayofthesys-com-docker-login" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "10308648" -> null
          - uid              = "39c14951-3935-491c-a662-1949184c2a29" -> null
        }
    }

  # kubernetes_secret.mongodb_root_password will be destroyed
- resource "kubernetes_secret" "mongodb_root_password" {
      - data      = (sensitive value)
      - id        = "pritunl/mongodb-root-password" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/Opaque" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "mongodb-root-password" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "14437265" -> null
          - uid              = "808ed55a-b973-4ef4-be80-746b5bba31aa" -> null
        }
    }

  # kubernetes_secret.tls must be replaced
-/+ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
      ~ id        = "pritunl/wayofthesys-com-pritunl-tls" -> (known after apply)
      - immutable = false -> null
        # (1 unchanged attribute hidden)

      ~ metadata {
          - annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              - "cert-manager.io/ip-sans"          = ""
              - "cert-manager.io/issuer-group"     = "cert-manager.io"
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              - "cert-manager.io/issuer-name"      = "zerossl"
              - "cert-manager.io/uri-sans"         = ""
            } -> null
          ~ generation       = 0 -> (known after apply)
          - labels           = {} -> null
          ~ name             = "wayofthesys-com-pritunl-tls" -> "wayofthesys-com-terraform-tls" # forces replacement
          ~ resource_version = "14765735" -> (known after apply)
          ~ uid              = "659f3168-c70e-424f-a02e-14750f65eeba" -> (known after apply)
            # (1 unchanged attribute hidden)
        }
    }

  # random_id.encryption-key will be destroyed
- resource "random_id" "encryption-key" {
      - b64_std     = "GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns=" -> null
      - b64_url     = "GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns" -> null
      - byte_length = 32 -> null
      - dec         = "11761591974363863710888702749719167498629641427876505890593812923174025195131" -> null
      - hex         = "1a00d33cee8e8b5cb38407e29a2ca4e62c01b036234076cf2c3c7b9fc9586e7b" -> null
      - id          = "GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns" -> null
    }

  # tls_cert_request.request must be replaced
-/+ resource "tls_cert_request" "request" {
      ~ cert_request_pem = <<-EOT
            -----BEGIN CERTIFICATE REQUEST-----
            MIIDBjCCAe4CAQAwNTERMA8GA1UEChMIQXRsYW50aXMxIDAeBgNVBAMTF3ByaXR1
            bmwud2F5b2Z0aGVzeXMuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
            AQEA5lJDYAk0g4CxkJCu6amgCAZ2ISd7rvsuvGJNP+h/BS/6N1VtDxuNm/kVkUGR
            HJ+hjgDI8h0c8B9V5zJsQVf/vohlYFDfzysiME0hwejyXiaPaeSMX0VZRUqVGBNG
            08/MIwGncogGau8Rk5zXoF7tBHjIPMlU5oNorLS95Mfl5FqC/Uz2kARNBcPPPpbp
            gkb9aJymPgIQf9cmIqXqlXQesNMueCyLlXNgy6k9uaLE4TlihNUhUOhKppT+Oi/j
            KCY+tsv5+utzopPimJeb90E+5froxRAjKMlJ0MW+0DHTqsZD2gnmPwnaRZ73wma3
            rZMmUCrWdgNCA2cov/hSRUy8GwIDAQABoIGLMIGIBgkqhkiG9w0BCQ4xezB5MHcG
            A1UdEQRwMG6CCGF0bGFudGlzgg5hdGxhbnRpcy5sb2NhbIIiYXRsYW50aXMuZGVm
            YXVsdC5zdmMuY2x1c3Rlci5sb2NhbIIJbG9jYWxob3N0ghdwcml0dW5sLndheW9m
            dGhlc3lzLmNvbYcEfwAAAYcEisUw9zANBgkqhkiG9w0BAQsFAAOCAQEA1zteii8W
            xXoU420RsJSglP0n7BycQZlQZNpStXRTC0jgtLLGTOtBNVAuCMq8QzjHN7xL6okF
            3NUAJDyah73uqR29Hj2z3Us4olor55I5K0lDAn4Y3NprDWth9ejsYv0eiLhqC0b9
            5BLq+mM5FhKEcEVSlwiymUSxw3StnvCVf2gKDoBKdgd3eyEipayLU7O2ZAvc/AUv
            0DEtcF5gvrApvpE51FE6+CPuoXUjnRTgzXF3H3JZhIGiz/Ayp7P8btO/+KT2lj58
            Nwey93q46AUBQlbll6SMPzuqGf/brbsG3c4PaTmp8eFtKQ9iXUhW/hNxcrqWUJd/
            e6IPU2beys5KvQ==
            -----END CERTIFICATE REQUEST-----
        EOT -> (known after apply)
      ~ dns_names        = [ # forces replacement
            # (3 unchanged elements hidden)
            "localhost",
          - "pritunl.wayofthesys.com",
          + "terraform.wayofthesys.com",
        ]
      ~ id               = "bd65263b60fe87b500efff18a405fa1f641dcdc5" -> (known after apply)
        # (3 unchanged attributes hidden)

      ~ subject {
          ~ common_name    = "pritunl.wayofthesys.com" -> "terraform.wayofthesys.com" # forces replacement
          - street_address = [] -> null
            # (1 unchanged attribute hidden)
        }
    }

  # tls_locally_signed_cert.cert must be replaced
-/+ resource "tls_locally_signed_cert" "cert" {
      ~ cert_pem              = <<-EOT
            -----BEGIN CERTIFICATE-----
            MIIDvzCCAqegAwIBAgIQU3KtzUKiTvWlntHnR4e1BDANBgkqhkiG9w0BAQsFADAl
            MRAwDgYDVQQKEwdQcml0dW5sMREwDwYDVQQDEwhjYS5sb2NhbDAeFw0yMjA0MTky
            MDMwNTRaFw0yMzA0MTkyMDMwNTRaMDUxETAPBgNVBAoTCEF0bGFudGlzMSAwHgYD
            VQQDExdwcml0dW5sLndheW9mdGhlc3lzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQAD
            ggEPADCCAQoCggEBAOZSQ2AJNIOAsZCQrumpoAgGdiEne677LrxiTT/ofwUv+jdV
            bQ8bjZv5FZFBkRyfoY4AyPIdHPAfVecybEFX/76IZWBQ388rIjBNIcHo8l4mj2nk
            jF9FWUVKlRgTRtPPzCMBp3KIBmrvEZOc16Be7QR4yDzJVOaDaKy0veTH5eRagv1M
            9pAETQXDzz6W6YJG/Wicpj4CEH/XJiKl6pV0HrDTLngsi5VzYMupPbmixOE5YoTV
            IVDoSqaU/jov4ygmPrbL+frrc6KT4piXm/dBPuX66MUQIyjJSdDFvtAx06rGQ9oJ
            5j8J2kWe98Jmt62TJlAq1nYDQgNnKL/4UkVMvBsCAwEAAaOB2jCB1zAOBgNVHQ8B
            Af8EBAMCAqQwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMAwGA1UdEwEB
            /wQCMAAwHwYDVR0jBBgwFoAUiX7mn7B4BkrbgISk8XecJhMj9owwdwYDVR0RBHAw
            boIIYXRsYW50aXOCDmF0bGFudGlzLmxvY2FsgiJhdGxhbnRpcy5kZWZhdWx0LnN2
            Yy5jbHVzdGVyLmxvY2Fsgglsb2NhbGhvc3SCF3ByaXR1bmwud2F5b2Z0aGVzeXMu
            Y29thwR/AAABhwSKxTD3MA0GCSqGSIb3DQEBCwUAA4IBAQCJnXZZkFrA8AbAhxZz
            fIYbBARiW13Uk5dGrUGxkBdeNdqsMO+fQnYnoXTqyeLR4HOmGnosnD41rgu0q3zp
            NnywD8doUEQHwiysSw66OX5eXGMc46oHIsqoNv0PnvMtMTbR7D475a6iHvUFyC2R
            ajmSsHyajH8tyid9z6JSpIngp7Pga95KiGTOchK++XjOMzmpGpsO8TJmbQ2AtG7v
            yeMZOtx+96rtebbWVYweR3DJ0r4WeTzq14A6NTXYACLo44elrFBwYooMACaxSkC5
            XNnL4HWBijdaulsnLkxd0UC+6ocopWRtq1tlsfpsjENVgZH4UEcxv+6XdBrR7pzT
            YmNo
            -----END CERTIFICATE-----
        EOT -> (known after apply)
      ~ cert_request_pem      = "fe3bd1e0ff62625977693dacce4477b4d9125881" -> (known after apply) # forces replacement
      ~ id                    = "110921370611277964470799525342932874500" -> (known after apply)
      ~ ready_for_renewal     = false -> true
      ~ validity_end_time     = "2023-04-19T20:30:54.793906102Z" -> (known after apply)
      ~ validity_start_time   = "2022-04-19T20:30:54.793906102Z" -> (known after apply)
        # (6 unchanged attributes hidden)
    }

Plan: 4 to add, 1 to change, 7 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 20, in resource "tls_self_signed_cert" "ca":
  20:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 4 to add, 1 to change, 7 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14762570" -> "14765735"
            # (4 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:
~ update in-place
- destroy
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # helm_release.mongodb must be replaced
-/+ resource "helm_release" "mongodb" {
      ~ id                         = "pritunl-mongodb" -> (known after apply)
      + manifest                   = (known after apply)
      ~ metadata                   = [
          - {
              - app_version = "4.4.13"
              - chart       = "mongodb"
              - name        = "pritunl-mongodb"
              - namespace   = "pritunl"
              - revision    = 2
              - values      = jsonencode(
                    {
                      - auth = {
                          - database     = "pritunl"
                          - password     = "IJfedsdaHHffhd323a"
                          - rootPassword = "IJfedsdaHHffhd323a"
                          - rootUser     = "admin"
                          - username     = "admin"
                        }
                    }
                )
              - version     = "11.1.2"
            },
        ] -> (known after apply)
      ~ name                       = "pritunl-mongodb" -> "mongodb" # forces replacement
      ~ namespace                  = "pritunl" -> "mongodb" # forces replacement
      ~ repository                 = "./helm_charts" -> "https://charts.bitnami.com/bitnami"
      - values                     = [
          - (sensitive),
        ] -> null
        # (23 unchanged attributes hidden)
    }

  # helm_release.pritunl will be updated in-place
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ values                     = [
          - <<-EOT
                image:
                  registry: ghcr.io
                  repository: autotune/pritunl-k8s-tf-do/autotune/pritunl-k8s-tf-do
                  tag: pritunl:dc7700e4
                  pullPolicy: Always
                  pullSecret: "wayofthesys-com-docker-login"
                  domain_name: "wayofthesys-com"

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 80

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
          + <<-EOT
                image:
                  registry: docker.pkg.github.com
                  repository: autotune/pritunl-k8s-tf-do
                  tag: latest
                  pullPolicy: Always

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 443

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
        ]
      ~ version                    = "0.0.8" -> "0.0.1"
        # (25 unchanged attributes hidden)
    }

  # kubernetes_secret.docker_login_secret will be destroyed
- resource "kubernetes_secret" "docker_login_secret" {
      - data      = (sensitive value)
      - id        = "pritunl/wayofthesys-com-docker-login" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/dockerconfigjson" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "wayofthesys-com-docker-login" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "10308648" -> null
          - uid              = "39c14951-3935-491c-a662-1949184c2a29" -> null
        }
    }

  # kubernetes_secret.mongodb_root_password will be destroyed
- resource "kubernetes_secret" "mongodb_root_password" {
      - data      = (sensitive value)
      - id        = "pritunl/mongodb-root-password" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/Opaque" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "mongodb-root-password" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "14437265" -> null
          - uid              = "808ed55a-b973-4ef4-be80-746b5bba31aa" -> null
        }
    }

  # kubernetes_secret.tls must be replaced
-/+ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
      ~ id        = "pritunl/wayofthesys-com-pritunl-tls" -> (known after apply)
      - immutable = false -> null
        # (1 unchanged attribute hidden)

      ~ metadata {
          - annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              - "cert-manager.io/ip-sans"          = ""
              - "cert-manager.io/issuer-group"     = "cert-manager.io"
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              - "cert-manager.io/issuer-name"      = "zerossl"
              - "cert-manager.io/uri-sans"         = ""
            } -> null
          ~ generation       = 0 -> (known after apply)
          - labels           = {} -> null
          ~ name             = "wayofthesys-com-pritunl-tls" -> "wayofthesys-com-terraform-tls" # forces replacement
          ~ resource_version = "14765735" -> (known after apply)
          ~ uid              = "659f3168-c70e-424f-a02e-14750f65eeba" -> (known after apply)
            # (1 unchanged attribute hidden)
        }
    }

  # random_id.encryption-key will be destroyed
- resource "random_id" "encryption-key" {
      - b64_std     = "GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns=" -> null
      - b64_url     = "GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns" -> null
      - byte_length = 32 -> null
      - dec         = "11761591974363863710888702749719167498629641427876505890593812923174025195131" -> null
      - hex         = "1a00d33cee8e8b5cb38407e29a2ca4e62c01b036234076cf2c3c7b9fc9586e7b" -> null
      - id          = "GgDTPO6Oi1yzhAfimiyk5iwBsDYjQHbPLDx7n8lYbns" -> null
    }

  # tls_cert_request.request must be replaced
-/+ resource "tls_cert_request" "request" {
      ~ cert_request_pem = <<-EOT
            -----BEGIN CERTIFICATE REQUEST-----
            MIIDBjCCAe4CAQAwNTERMA8GA1UEChMIQXRsYW50aXMxIDAeBgNVBAMTF3ByaXR1
            bmwud2F5b2Z0aGVzeXMuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKC
            AQEA5lJDYAk0g4CxkJCu6amgCAZ2ISd7rvsuvGJNP+h/BS/6N1VtDxuNm/kVkUGR
            HJ+hjgDI8h0c8B9V5zJsQVf/vohlYFDfzysiME0hwejyXiaPaeSMX0VZRUqVGBNG
            08/MIwGncogGau8Rk5zXoF7tBHjIPMlU5oNorLS95Mfl5FqC/Uz2kARNBcPPPpbp
            gkb9aJymPgIQf9cmIqXqlXQesNMueCyLlXNgy6k9uaLE4TlihNUhUOhKppT+Oi/j
            KCY+tsv5+utzopPimJeb90E+5froxRAjKMlJ0MW+0DHTqsZD2gnmPwnaRZ73wma3
            rZMmUCrWdgNCA2cov/hSRUy8GwIDAQABoIGLMIGIBgkqhkiG9w0BCQ4xezB5MHcG
            A1UdEQRwMG6CCGF0bGFudGlzgg5hdGxhbnRpcy5sb2NhbIIiYXRsYW50aXMuZGVm
            YXVsdC5zdmMuY2x1c3Rlci5sb2NhbIIJbG9jYWxob3N0ghdwcml0dW5sLndheW9m
            dGhlc3lzLmNvbYcEfwAAAYcEisUw9zANBgkqhkiG9w0BAQsFAAOCAQEA1zteii8W
            xXoU420RsJSglP0n7BycQZlQZNpStXRTC0jgtLLGTOtBNVAuCMq8QzjHN7xL6okF
            3NUAJDyah73uqR29Hj2z3Us4olor55I5K0lDAn4Y3NprDWth9ejsYv0eiLhqC0b9
            5BLq+mM5FhKEcEVSlwiymUSxw3StnvCVf2gKDoBKdgd3eyEipayLU7O2ZAvc/AUv
            0DEtcF5gvrApvpE51FE6+CPuoXUjnRTgzXF3H3JZhIGiz/Ayp7P8btO/+KT2lj58
            Nwey93q46AUBQlbll6SMPzuqGf/brbsG3c4PaTmp8eFtKQ9iXUhW/hNxcrqWUJd/
            e6IPU2beys5KvQ==
            -----END CERTIFICATE REQUEST-----
        EOT -> (known after apply)
      ~ dns_names        = [ # forces replacement
            # (3 unchanged elements hidden)
            "localhost",
          - "pritunl.wayofthesys.com",
          + "terraform.wayofthesys.com",
        ]
      ~ id               = "bd65263b60fe87b500efff18a405fa1f641dcdc5" -> (known after apply)
        # (3 unchanged attributes hidden)

      ~ subject {
          ~ common_name    = "pritunl.wayofthesys.com" -> "terraform.wayofthesys.com" # forces replacement
          - street_address = [] -> null
            # (1 unchanged attribute hidden)
        }
    }

  # tls_locally_signed_cert.cert must be replaced
-/+ resource "tls_locally_signed_cert" "cert" {
      ~ cert_pem              = <<-EOT
            -----BEGIN CERTIFICATE-----
            MIIDvzCCAqegAwIBAgIQU3KtzUKiTvWlntHnR4e1BDANBgkqhkiG9w0BAQsFADAl
            MRAwDgYDVQQKEwdQcml0dW5sMREwDwYDVQQDEwhjYS5sb2NhbDAeFw0yMjA0MTky
            MDMwNTRaFw0yMzA0MTkyMDMwNTRaMDUxETAPBgNVBAoTCEF0bGFudGlzMSAwHgYD
            VQQDExdwcml0dW5sLndheW9mdGhlc3lzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQAD
            ggEPADCCAQoCggEBAOZSQ2AJNIOAsZCQrumpoAgGdiEne677LrxiTT/ofwUv+jdV
            bQ8bjZv5FZFBkRyfoY4AyPIdHPAfVecybEFX/76IZWBQ388rIjBNIcHo8l4mj2nk
            jF9FWUVKlRgTRtPPzCMBp3KIBmrvEZOc16Be7QR4yDzJVOaDaKy0veTH5eRagv1M
            9pAETQXDzz6W6YJG/Wicpj4CEH/XJiKl6pV0HrDTLngsi5VzYMupPbmixOE5YoTV
            IVDoSqaU/jov4ygmPrbL+frrc6KT4piXm/dBPuX66MUQIyjJSdDFvtAx06rGQ9oJ
            5j8J2kWe98Jmt62TJlAq1nYDQgNnKL/4UkVMvBsCAwEAAaOB2jCB1zAOBgNVHQ8B
            Af8EBAMCAqQwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMAwGA1UdEwEB
            /wQCMAAwHwYDVR0jBBgwFoAUiX7mn7B4BkrbgISk8XecJhMj9owwdwYDVR0RBHAw
            boIIYXRsYW50aXOCDmF0bGFudGlzLmxvY2FsgiJhdGxhbnRpcy5kZWZhdWx0LnN2
            Yy5jbHVzdGVyLmxvY2Fsgglsb2NhbGhvc3SCF3ByaXR1bmwud2F5b2Z0aGVzeXMu
            Y29thwR/AAABhwSKxTD3MA0GCSqGSIb3DQEBCwUAA4IBAQCJnXZZkFrA8AbAhxZz
            fIYbBARiW13Uk5dGrUGxkBdeNdqsMO+fQnYnoXTqyeLR4HOmGnosnD41rgu0q3zp
            NnywD8doUEQHwiysSw66OX5eXGMc46oHIsqoNv0PnvMtMTbR7D475a6iHvUFyC2R
            ajmSsHyajH8tyid9z6JSpIngp7Pga95KiGTOchK++XjOMzmpGpsO8TJmbQ2AtG7v
            yeMZOtx+96rtebbWVYweR3DJ0r4WeTzq14A6NTXYACLo44elrFBwYooMACaxSkC5
            XNnL4HWBijdaulsnLkxd0UC+6ocopWRtq1tlsfpsjENVgZH4UEcxv+6XdBrR7pzT
            YmNo
            -----END CERTIFICATE-----
        EOT -> (known after apply)
      ~ cert_request_pem      = "fe3bd1e0ff62625977693dacce4477b4d9125881" -> (known after apply) # forces replacement
      ~ id                    = "110921370611277964470799525342932874500" -> (known after apply)
      ~ ready_for_renewal     = false -> true
      ~ validity_end_time     = "2023-04-19T20:30:54.793906102Z" -> (known after apply)
      ~ validity_start_time   = "2022-04-19T20:30:54.793906102Z" -> (known after apply)
        # (6 unchanged attributes hidden)
    }

Plan: 4 to add, 1 to change, 7 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 20, in resource "tls_self_signed_cert" "ca":
  20:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 4 to add, 1 to change, 7 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis unlock

All Atlantis locks for this PR have been unlocked and plans discarded

Ran Plan for dir: terraform/atlantis workspace: default
Plan Failed: This project is currently locked by an unapplied plan from pull #7. To continue, delete the lock from #7 or apply that plan and merge the pull request.
Once the lock is released, comment atlantis plan here to re-plan.

atlantis plan

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14762570" -> "14765735"
            # (4 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:
~ update in-place
- destroy
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # helm_release.mongodb must be replaced
-/+ resource "helm_release" "mongodb" {
      ~ id                         = "pritunl-mongodb" -> (known after apply)
      + manifest                   = (known after apply)
      ~ metadata                   = [
          - {
              - app_version = "4.4.13"
              - chart       = "mongodb"
              - name        = "pritunl-mongodb"
              - namespace   = "pritunl"
              - revision    = 2
              - values      = jsonencode(
                    {
                      - auth = {
                          - database     = "pritunl"
                          - password     = "IJfedsdaHHffhd323a"
                          - rootPassword = "IJfedsdaHHffhd323a"
                          - rootUser     = "admin"
                          - username     = "admin"
                        }
                    }
                )
              - version     = "11.1.2"
            },
        ] -> (known after apply)
      ~ name                       = "pritunl-mongodb" -> "mongodb" # forces replacement
      ~ namespace                  = "pritunl" -> "mongodb" # forces replacement
      ~ repository                 = "./helm_charts" -> "https://charts.bitnami.com/bitnami"
      - values                     = [
          - (sensitive),
        ] -> null
        # (23 unchanged attributes hidden)
    }

  # helm_release.pritunl will be updated in-place
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ values                     = [
          - <<-EOT
                image:
                  registry: ghcr.io
                  repository: autotune/pritunl-k8s-tf-do/autotune/pritunl-k8s-tf-do
                  tag: pritunl:dc7700e4
                  pullPolicy: Always
                  pullSecret: "wayofthesys-com-docker-login"
                  domain_name: "wayofthesys-com"

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 80

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
          + <<-EOT
                image:
                  registry: docker.pkg.github.com
                  repository: autotune/pritunl-k8s-tf-do
                  tag: latest
                  pullPolicy: Always

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 443

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
        ]
      ~ version                    = "0.0.8" -> "0.0.1"
        # (25 unchanged attributes hidden)
    }

  # kubernetes_secret.docker_login_secret will be destroyed
- resource "kubernetes_secret" "docker_login_secret" {
      - data      = (sensitive value)
      - id        = "pritunl/wayofthesys-com-docker-login" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/dockerconfigjson" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "wayofthesys-com-docker-login" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "10308648" -> null
          - uid              = "39c14951-3935-491c-a662-1949184c2a29" -> null
        }
    }

  # kubernetes_secret.mongodb_root_password will be destroyed
- resource "kubernetes_secret" "mongodb_root_password" {
      - data      = (sensitive value)
      - id        = "pritunl/mongodb-root-password" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/Opaque" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "mongodb-root-password" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "14437265" -> null
          - uid              = "808ed55a-b973-4ef4-be80-746b5bba31aa" -> null
        }
    }

  # kubernetes_secret.tls will be updated in-place
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls" -> null
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/ip-sans"          = "" -> null
              - "cert-manager.io/issuer-group"     = "cert-manager.io" -> null
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer" -> null
              - "cert-manager.io/issuer-name"      = "zerossl" -> null
              - "cert-manager.io/uri-sans"         = "" -> null
            }
            name             = "wayofthesys-com-pritunl-tls"
            # (5 unchanged attributes hidden)
        }
    }

Plan: 1 to add, 2 to change, 3 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 1 to add, 2 to change, 3 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Ran Plan for dir: terraform/atlantis workspace: default
Plan Error
Show Output
running "/usr/local/bin/terraform plan -input=false -refresh -no-color -out \"/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis/default.tfplan\"" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis": exit status 1

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 2 more similar warnings elsewhere)

Error: Reference to undeclared input variable

  on data.tf line 5, in data "template_file" "pritunl":
   5:     DOCKER_REPO     = "${var.gh_username}/pritunl-k8s-tf-do"

An input variable with the name "gh_username" has not been declared. This
variable can be declared with a variable "gh_username" {} block.

Error: Reference to undeclared local value

  on data.tf line 15, in data "template_file" "docker_registry":
  15:     docker_secret_encoded = local.docker_secret_encoded

A local value with the name "docker_secret_encoded" has not been declared.

Error: Invalid function argument

  on data.tf line 20, in data "template_file" "mongodb":
  20:   template = file("${path.module}/mongodb/values.yaml.tpl")
    ├────────────────
    │ path.module is "."

Invalid value for "path" parameter: no file exists at
./mongodb/values.yaml.tpl; this function works only with files that are
distributed as part of the configuration source code, so if this file will be
created by a resource in this configuration you must instead obtain this
result from an attribute of that resource.

Ran Plan for dir: terraform/atlantis workspace: default
Plan Error
Show Output
running "/usr/local/bin/terraform plan -input=false -refresh -no-color -out \"/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis/default.tfplan\"" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis": exit status 1

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 2 more similar warnings elsewhere)

Error: Reference to undeclared local value

  on data.tf line 15, in data "template_file" "docker_registry":
  15:     docker_secret_encoded = local.docker_secret_encoded

A local value with the name "docker_secret_encoded" has not been declared.

Error: Invalid function argument

  on data.tf line 20, in data "template_file" "mongodb":
  20:   template = file("${path.module}/mongodb/values.yaml.tpl")
    ├────────────────
    │ path.module is "."

Invalid value for "path" parameter: no file exists at
./mongodb/values.yaml.tpl; this function works only with files that are
distributed as part of the configuration source code, so if this file will be
created by a resource in this configuration you must instead obtain this
result from an attribute of that resource.

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14762570" -> "14765735"
            # (4 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:
~ update in-place
- destroy

Terraform will perform the following actions:

  # helm_release.mongodb will be updated in-place
~ resource "helm_release" "mongodb" {
        id                         = "pritunl-mongodb"
        name                       = "pritunl-mongodb"
      ~ version                    = "11.1.2" -> "11.1.1"
        # (26 unchanged attributes hidden)
    }

  # helm_release.pritunl will be updated in-place
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ values                     = [
          - <<-EOT
                image:
                  registry: ghcr.io
                  repository: autotune/pritunl-k8s-tf-do/autotune/pritunl-k8s-tf-do
                  tag: pritunl:dc7700e4
                  pullPolicy: Always
                  pullSecret: "wayofthesys-com-docker-login"
                  domain_name: "wayofthesys-com"

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 80

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
          + <<-EOT
                image:
                  registry: docker.pkg.github.com
                  repository: autotune/pritunl-k8s-tf-do
                  tag: latest
                  pullPolicy: Always

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 443

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
        ]
      ~ version                    = "0.0.8" -> "0.0.1"
        # (25 unchanged attributes hidden)
    }

  # kubernetes_secret.docker_login_secret will be destroyed
- resource "kubernetes_secret" "docker_login_secret" {
      - data      = (sensitive value)
      - id        = "pritunl/wayofthesys-com-docker-login" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/dockerconfigjson" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "wayofthesys-com-docker-login" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "10308648" -> null
          - uid              = "39c14951-3935-491c-a662-1949184c2a29" -> null
        }
    }

  # kubernetes_secret.mongodb_root_password will be destroyed
- resource "kubernetes_secret" "mongodb_root_password" {
      - data      = (sensitive value)
      - id        = "pritunl/mongodb-root-password" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/Opaque" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "mongodb-root-password" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "14437265" -> null
          - uid              = "808ed55a-b973-4ef4-be80-746b5bba31aa" -> null
        }
    }

  # kubernetes_secret.tls will be updated in-place
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls" -> null
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/ip-sans"          = "" -> null
              - "cert-manager.io/issuer-group"     = "cert-manager.io" -> null
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer" -> null
              - "cert-manager.io/issuer-name"      = "zerossl" -> null
              - "cert-manager.io/uri-sans"         = "" -> null
            }
            name             = "wayofthesys-com-pritunl-tls"
            # (5 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 3 to change, 2 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 0 to add, 3 to change, 2 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14762570" -> "14765735"
            # (4 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:
~ update in-place
- destroy

Terraform will perform the following actions:

  # helm_release.pritunl will be updated in-place
~ resource "helm_release" "pritunl" {
        id                         = "pritunl"
        name                       = "pritunl"
      ~ values                     = [
          - <<-EOT
                image:
                  registry: ghcr.io
                  repository: autotune/pritunl-k8s-tf-do/autotune/pritunl-k8s-tf-do
                  tag: pritunl:dc7700e4
                  pullPolicy: Always
                  pullSecret: "wayofthesys-com-docker-login"
                  domain_name: "wayofthesys-com"

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 80

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
          + <<-EOT
                image:
                  registry: docker.pkg.github.com
                  repository: autotune/pritunl-k8s-tf-do
                  tag: latest
                  pullPolicy: Always

                # This should match whatever the 'mongodb' service is called in the cluster.
                # DNS should be able to resolve the service by this name for Pritunl to function.
                mongoService: "pritunl-mongodb"

                # Change these as you see fit.
                ports:
                  http: 80
                  vpn: 1194
                  webui: 443

                # This must be enabled when using Pritunl due to the rights that iptables will need in the Pritunl pods.
                privileged:
                  enabled: true

                # This will adjust the replicas that are deployed as a part of the Pritunl deployment.
                # This is '3' by default. Your Pritunl cluster number will be affected by this.
                replicaCount: 3

                # If 'type' here is 'LoadBalancer', these annotations are necessary to properly use an ELB if deploying this chart in AWS, so they'll automatically get used.
                # Be sure to add the appropriate domain name, cert ARN, and ssl-negotiation-policy (a default is used here).
                service:
                  annotations:
                  type: ClusterIP

                tty:
                  enabled: true

                # Health Checks
                livenessProbe:
                  enabled: true
                  initialDelaySeconds: 30
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1

                readinessProbe:
                  enabled: true
                  initialDelaySeconds: 5
                  periodSeconds: 10
                  timeoutSeconds: 5
                  failureThreshold: 6
                  successThreshold: 1
            EOT,
        ]
      ~ version                    = "0.0.8" -> "0.0.1"
        # (25 unchanged attributes hidden)
    }

  # kubernetes_secret.docker_login_secret will be destroyed
- resource "kubernetes_secret" "docker_login_secret" {
      - data      = (sensitive value)
      - id        = "pritunl/wayofthesys-com-docker-login" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/dockerconfigjson" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "wayofthesys-com-docker-login" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "10308648" -> null
          - uid              = "39c14951-3935-491c-a662-1949184c2a29" -> null
        }
    }

  # kubernetes_secret.mongodb_root_password will be destroyed
- resource "kubernetes_secret" "mongodb_root_password" {
      - data      = (sensitive value)
      - id        = "pritunl/mongodb-root-password" -> null
      - immutable = false -> null
      - type      = "kubernetes.io/Opaque" -> null

      - metadata {
          - annotations      = {} -> null
          - generation       = 0 -> null
          - labels           = {} -> null
          - name             = "mongodb-root-password" -> null
          - namespace        = "pritunl" -> null
          - resource_version = "14437265" -> null
          - uid              = "808ed55a-b973-4ef4-be80-746b5bba31aa" -> null
        }
    }

  # kubernetes_secret.tls will be updated in-place
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls" -> null
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/ip-sans"          = "" -> null
              - "cert-manager.io/issuer-group"     = "cert-manager.io" -> null
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer" -> null
              - "cert-manager.io/issuer-name"      = "zerossl" -> null
              - "cert-manager.io/uri-sans"         = "" -> null
            }
            name             = "wayofthesys-com-pritunl-tls"
            # (5 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 2 to change, 2 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 0 to add, 2 to change, 2 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

Ran Plan for dir: terraform/atlantis workspace: default
Plan Error
Show Output
running "/usr/local/bin/terraform plan -input=false -refresh -no-color -out \"/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis/default.tfplan\"" in "/root/.atlantis/repos/autotune/pritunl-k8s-tf-do/8/default/terraform/atlantis": exit status 1

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 2 more similar warnings elsewhere)

Error: Reference to undeclared resource

  on pritunl.tf line 10, in resource "helm_release" "pritunl":
  10:   depends_on = [kubernetes_namespace.pritunl, helm_release.mongodb, kubernetes_secret.docker_login_secret, kubernetes_secret.mongodb_root_password]

A managed resource "kubernetes_secret" "docker_login_secret" has not been
declared in the root module.

Ran Plan for dir: terraform/atlantis workspace: default
Show Output

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the
last "terraform apply":

  # kubernetes_secret.tls has been changed
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              + "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com"
              + "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls"
              + "cert-manager.io/common-name"      = "pritunl.wayofthesys.com"
              + "cert-manager.io/ip-sans"          = ""
              + "cert-manager.io/issuer-group"     = "cert-manager.io"
              + "cert-manager.io/issuer-kind"      = "ClusterIssuer"
              + "cert-manager.io/issuer-name"      = "zerossl"
              + "cert-manager.io/uri-sans"         = ""
            }
            name             = "wayofthesys-com-pritunl-tls"
          ~ resource_version = "14762570" -> "14765735"
            # (4 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:
~ update in-place

Terraform will perform the following actions:

  # kubernetes_secret.tls will be updated in-place
~ resource "kubernetes_secret" "tls" {
      ~ data      = (sensitive value)
        id        = "pritunl/wayofthesys-com-pritunl-tls"
        # (2 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "cert-manager.io/alt-names"        = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/certificate-name" = "wayofthesys-com-pritunl-tls" -> null
              - "cert-manager.io/common-name"      = "pritunl.wayofthesys.com" -> null
              - "cert-manager.io/ip-sans"          = "" -> null
              - "cert-manager.io/issuer-group"     = "cert-manager.io" -> null
              - "cert-manager.io/issuer-kind"      = "ClusterIssuer" -> null
              - "cert-manager.io/issuer-name"      = "zerossl" -> null
              - "cert-manager.io/uri-sans"         = "" -> null
            }
            name             = "wayofthesys-com-pritunl-tls"
            # (5 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Warning: Argument is deprecated

  with tls_self_signed_cert.ca,
  on tls.tf line 24, in resource "tls_self_signed_cert" "ca":
  24:   key_algorithm   = tls_private_key.ca.algorithm

This is now ignored, as the key algorithm is inferred from the
`private_key_pem`.

(and 5 more similar warnings elsewhere)

:arrow_forward: To apply this plan, comment:

atlantis apply -d terraform/atlantis

:put_litter_in_its_place: To delete this plan click here
:repeat: To plan this project again, comment:

atlantis plan -d terraform/atlantis

Plan: 0 to add, 1 to change, 0 to destroy.

:fast_forward: To apply all unapplied plans from this pull request, comment:

atlantis apply

:put_litter_in_its_place: To delete all plans and locks for the PR, comment:

atlantis unlock

atlantis apply -d terraform/atlantis

Ran Apply for dir: terraform/atlantis workspace: default
Show Output
kubernetes_secret.tls: Modifying... [id=pritunl/wayofthesys-com-pritunl-tls]
kubernetes_secret.tls: Modifications complete after 0s [id=pritunl/wayofthesys-com-pritunl-tls]

Warning: Version constraints inside provider configuration blocks are deprecated

  on providers.tf line 12, in provider "digitalocean":
  12:   version = ">=1.5.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

atlantis unlock

All Atlantis locks for this PR have been unlocked and plans discarded


Fix issue template to not apply Kubernetes SIGS

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Let's do not label them this way to keep the project clean.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/retest

/lgtm


How can I start to contribute?

I can see lots of TODO in the code, but I don't know which one I should pick up first. Do you have any issue that you can assign to me to get more familiar with the code base?

Hi, thanks for reaching out. I guess this: https://github.com/noib3/nvim-compleet/blob/08cd0763f7ba2f62835565c045933b5f66780061/src/ui/details/positioning.rs#L78
would be a good place to start. It's a bug with the positioning of the details window (i.e. the window next to the completion menu that shows details about a completion) that causes nvim-compleet to panic.
Demo:

to reproduce:

compile from commit 08cd0763f7ba2f62835565c045933b5f66780061;
set the columns to 173 (altough it's probably possible to reproduce this with a different terminal width);
open a new vertical split to the right and go to that window;
type s;
select the first completion;
type i.

The reason is that api.win_get_position(menu_winid) (which is just a Rust binding to vim.api.nvim_win_get_position) returns a number of columns bigger than the total terminal width, causing the following unchecked subtractions to overflow.
I believe it's a bug with Neovim itself rather than nvim-compleet, but I haven't looked too much into it.
P.S.: this is just a suggestion, if you'd like to work on something else feel free to do so. Also, if you'd like to contact me send me a DM on Telegram (https://t.me/noib3) or on matrix (@noib3:matrix.org).

thank you. I will put some time to investigate that one this weekend.

hmm, I can not reproduce that. set columns=173 and open new vsplit, but  don't know why my menu is different with you when I hit <c-n> to go to the next item. I also tried disabling all plugins but still the same.
https://user-images.githubusercontent.com/22189661/161381740-dcbe7cd7-2d9c-4e12-8624-f27f1eee6f63.mov

I think you haven't set the mappings to select the first completion. If that still doesn't work, try to replicate it by creating a minimal init.lua and calling neovim with nvim --clean -u ./init.lua.

Hi, I noticed you've been working on the back2rpc branch recently. Is that going to be the final architecture? Are you going to merge that eventually into master?


Download from specific position in playlist

Checklist

[x] I'm asking a question
[x] I've looked through the README and FAQ for similar questions
[x] I've searched the bugtracker for similar questions including closed ones

Question

Is it possible to start downloading from YouTube playlist from specific video (position)? I have downloaded yesterday just like half of playlist and turned the pc off. Today I want to continue downloading new videos and I don't want to have duplicate videos.

You can achieve this by using the --download-archive argument. It will store which videos have already been downloaded and not redownload them. To answer your original question it is possible to specify the start and end index of the playlist using the --playlist-start and --playlist-end arguments.
https://github.com/ytdl-org/youtube-dl#how-do-i-download-only-new-videos-from-a-playlist
https://github.com/ytdl-org/youtube-dl#video-selection

Read about --playlist-start ... and related options.

Thanks

Which file extension should I use for --download-archive option? Or you don't need to provide file name? Does it auto create the file and save IDs of downloaded songs to it?

If you actually read what the --help output says:
    --download-archive FILE              Download only videos not listed in the
                                         archive file. Record the IDs of all
                                         downloaded videos in it.

you'll see that you have to supply the filename. No-one else cares what you call it.


python310Packages.sounddevice: 0.4.5 -> 0.4.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.sounddevice is: Play and Record Sound with Python
meta.homepage for python310Packages.sounddevice is: http://python-sounddevice.rtfd.org/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.4.6 with grep in /nix/store/ysppi47pg0nfmjpw5b216ksl93wgj80c-python3.10-sounddevice-0.4.6
found 0.4.6 in filename of file in /nix/store/ysppi47pg0nfmjpw5b216ksl93wgj80c-python3.10-sounddevice-0.4.6

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
friture
python310Packages.dragonfly
python310Packages.rtmixer
python310Packages.sounddevice
python311Packages.dragonfly
python311Packages.rtmixer
python311Packages.sounddevice

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ysppi47pg0nfmjpw5b216ksl93wgj80c-python3.10-sounddevice-0.4.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.sounddevice https://github.com/r-ryantm/nixpkgs/archive/7a504fd9746775e2497663c8a223cf4e2589d569.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ysppi47pg0nfmjpw5b216ksl93wgj80c-python3.10-sounddevice-0.4.6
ls -la /nix/store/ysppi47pg0nfmjpw5b216ksl93wgj80c-python3.10-sounddevice-0.4.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

7 packages built:

friture
python310Packages.dragonfly
python310Packages.rtmixer
python310Packages.sounddevice
python311Packages.dragonfly
python311Packages.rtmixer
python311Packages.sounddevice

Maintainer pings
cc @FRidh for testing.

@ofborg build friture


bitcoin.update.sh update

the bitcoin update needs multiple refactoring:

[x] it needs to run non-interactive for provisioning
[x] it should just have a list if trusted signers and check if if those signed the release
[x] the "tested" should also work if the numer if stored in conf ins LOWER then the tested

last point is so that there could be multiple updates if tested version before a new sd card

Test with offering bitcoin v25.0 as update option

Also got a error report when somebody updating to bitcoin 25
/dev/fd/63: line 22: bitcoin-25.0-aarch64-linux-gnu.tar.gz:: command not found
/dev/fd/63: line 29: bitcoin-25.0/: No such file or directory
/dev/fd/63: line 30: bitcoin-25.0/[README.md](https://readme.md/): No such file or directory
/dev/fd/63: line 31: bitcoin-25.0/bin/: No such file or directory
/dev/fd/63: line 32: bitcoin-25.0/bin/bitcoin-cli: No such file or directory
/dev/fd/63: line 33: bitcoin-25.0/bin/bitcoin-qt: No such file or directory
/dev/fd/63: line 34: bitcoin-25.0/bin/bitcoin-tx: No such file or directory
/dev/fd/63: line 35: bitcoin-25.0/bin/bitcoin-util: No such file or directory
/dev/fd/63: line 36: bitcoin-25.0/bin/bitcoin-wallet: No such file or directory
/dev/fd/63: line 37: bitcoin-25.0/bin/bitcoind: No such file or directory
/dev/fd/63: line 38: bitcoin-25.0/bin/test_bitcoin: No such file or directory
/dev/fd/63: line 39: bitcoin-25.0/bitcoin.conf: No such file or directory
/dev/fd/63: line 40: bitcoin-25.0/include/: No such file or directory
/dev/fd/63: line 41: bitcoin-25.0/include/bitcoinconsensus.h: No such file or directory/dev/fd/63: line 42: bitcoin-25.0/lib/: No such file or directory
/dev/fd/63: line 43: bitcoin-25.0/lib/[libbitcoinconsensus.so](https://libbitcoinconsensus.so/): No such file or directory/dev/fd/63: line 44: bitcoin-25.0/lib/[libbitcoinconsensus.so](https://libbitcoinconsensus.so/).0: No such file or directory
/dev/fd/63: line 45: bitcoin-25.0/lib/[libbitcoinconsensus.so](https://libbitcoinconsensus.so/).0.0.0: No such file or directory
/dev/fd/63: line 46: bitcoin-25.0/share/: No such file or directory
/dev/fd/63: line 47: bitcoin-25.0/share/man/: No such file or directory
/dev/fd/63: line 48: bitcoin-25.0/share/man/man1/: No such file or directory
/dev/fd/63: line 49: bitcoin-25.0/share/man/man1/bitcoin-cli.1: No such file or directory
/dev/fd/63: line 50: bitcoin-25.0/share/man/man1/bitcoin-qt.1: No such file or directory
/dev/fd/63: line 51: bitcoin-25.0/share/man/man1/bitcoin-tx.1: No such file or directory
/dev/fd/63: line 52: bitcoin-25.0/share/man/man1/bitcoin-util.1: No such file or directory
/dev/fd/63: line 53: bitcoin-25.0/share/man/man1/bitcoin-wallet.1: No such file or directory
/dev/fd/63: line 54: bitcoin-25.0/share/man/man1/bitcoind.1: No such file or directory
/dev/fd/63: line 55: bitcoin-25.0/share/rpcauth/: No such file or directory
/dev/fd/63: line 56: bitcoin-25.0/share/rpcauth/[README.md](https://readme.md/): No such file or directory
/dev/fd/63: line 57: bitcoin-25.0/share/rpcauth/[rpcauth.py](https://rpcauth.py/): No such file or directory
/dev/fd/63: line 58: Bitcoin: command not found
Green activity light stays dark and LCD turns white when shutdown complete.
It will then reboot again automatically.
-----------------------------------------------
stop electrs - please wait ..
stop LNDg - please wait ..

Rewrite for a v1.10.1 or v1.11.0 release

I think this was solved in v1.11.1 ... but recheck

OK tested with v1.11.1 - already all good. Closing issue.


Resolved issues still not clearing from list

Referenced in #309 which is now closed - and supposedly fixed in 0.8.0, but I'm still experiencing the issue with resolved events not clearing from the active events list, despite being in the "resolved" state.
Any joy?

Hi,
Yes I'm experiencing the same, the api status is o, but its still hanging in the event list.
[root@sensu ~]# rpm -qa | grep sens
sensu-0.18.1-1.x86_64

[root@sensu ~]# rpm -qa | grep uchi
uchiwa-0.8.1-1.x86_64

This the sensu-client log output
{"timestamp":"2015-05-22T14:27:05.581789+0100","level":"info","message":"received check request","check":{"name":"check-cpu","issued":1432301225,"command":"/etc/sensu/checks/check-cpu.rb"}}
{"timestamp":"2015-05-22T14:27:07.555336+0100","level":"info","message":"publishing check result","payload":{"client":"abc.example.com","check":{"name":"check-cpu","issued":1432301225,"command":"/etc/sensu/checks/check-cpu.rb","executed":1432301225,"duration":1.973,"output":"CheckCPU TOTAL OK: total=10.0 user=7.0 nice=0.0 system=3.0 idle=90.0 iowait=0.0 irq=0.0 softirq=0.0 steal=0.0 guest=0.0\n","status":0}}}

Unfortunately I'm unable to reproduce this issue with the latest release (0.8.1) so I'll need your help to investigate.
Next time you see a resolved event into your events list, could you provide me the results from the following endpoints:

http://sensu-api-url:4567/events
http://uchiwa-url:3000/get_sensu

Thanks!

http://sensu-api-url:4567/events:
{
  "id": "1c1707f8-9bb1-4d52-b54b-31c194332f54",
  "client": {
    "name": "hostname.network.net",
    "address": "<IP_ADDRESS>",
    "bind": "<IP_ADDRESS>",
    "subscriptions": [
      "common"
    ],
    "safe_mode": false,
    "keepalive": {
      "high_flap_threshold": 20,
      "low_flap_threshold": 5,
      "refresh": 14400,
      "thresholds": {
        "critical": 120,
        "warning": 90
      }
    },
    "handlers": [
      "default"
    ],
    "version": "0.18.0",
    "timestamp":<PHONE_NUMBER>
  },
  "check": {
    "command": "check-ram.rb",
    "interval": 60,
    "handlers": [
      "default"
    ],
    "refresh": 1209600,
    "standalone": true,
    "high_flap_threshold": 20,
    "low_flap_threshold": 5,
    "name": "os-memory",
    "issued":<PHONE_NUMBER>,
    "executed":<PHONE_NUMBER>,
    "duration": 0.138,
    "output": "CheckRAM OK: 87% free RAM left\n",
    "status": 0,
    "history": [
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0",
      "0"
    ],
    "total_state_change": 0
  },
  "occurrences": 32659,
  "action": "flapping"
}```

I don't have access, currently, to the sensu backend itself, so I'll post the other result when I do

I was also still seeing this issue. I think if you're having this problem, you need to stop everything and issue a redis-cli flushall to clear out the cached event info. For me, the events did not just go away on their own after the upgrade (and full restart).

@jcmcken that seems to have fixed it, thanks!

@jcmcken :+1:

Hmm, actually I still might be seeing this issue. After doing the above, some new alerts came in and then resolved. Those alerts are still showing (as green) in the dashboard. I thought it might be because they're flapping, but their entire history window is now 0's and they still haven't disappeared.

@jcmcken Do you also see these resolved issues in the /events endpoint of your Sensu API? If so, I would recommend you to open an issue on the Sensu project so we can better assist you with this issue!

Thanks @palourde, you're right, this is probably not an uchiwa issue. I think the problem is in the logic which clears flapping alarms, I'll take a look at it and submit an issue over to Sensu.


Feature/profiler work

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: schmidtw:x: Harter, Nicholas (Contractor):x: joe94Harter, Nicholas (Contractor) seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #39 into master will decrease coverage by 7.32%.
The diff coverage is 18.75%.

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
- Coverage   58.62%   51.29%   -7.33%
==========================================
  Files           6        6
  Lines         406      464      +58
==========================================
  Hits          238      238
- Misses        161      215      +54
- Partials        7       11       +4

Impacted Files
Coverage Δ

src/caduceus/caduceus.go
0% <0%> (ø)
:arrow_up:

src/caduceus/http.go
80% <100%> (+0.31%)
:arrow_up:

src/caduceus/caduceusProfiler.go
45.54% <11.29%> (-54.46%)
:arrow_down:

src/caduceus/caduceus_type.go
71.79% <50%> (-2.02%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f40b441...266c639. Read the comment docs.


Unwanted Tampered detected issue

When downloading app from playstore with freeRASP in some devices, it is giving "Tampered Detected" error, whereas the device is not tampered.
Mostly we are observing this on Samsung and One plus devices.
Using freeRASP version 3.0.1.

Hello @meetp-interpay ,
please write us your watcherMail and package name at<EMAIL_ADDRESS>so we can take a deeper look at the logs.
Kind regards,
Talsec dev


How to select Studio driver?

Hi.
On the interactive website, I can select Studio or Game driver. Is it possible to choose this with your script?

Not possible right now but I do plan to support studio driver updating in the future.
I've been looking into ways of doing this in the past (see https://github.com/ElPumpo/TinyNvidiaUpdateChecker/issues/137#issuecomment-1352804241) but implementing this method of finding a new driver isn't ideal.
I recommend checking out NVIDIA-Driver-Downloader, which seems to have this functionality, though I've never tested it.

Thank you! I will check it tonight.


FEAT: Allow for modifying all output promptText with additional tmp rich text tags

First off just want to say great work!
My only issue is that I'm finding the icons to be too small when output in relation to my text when using the PrompText component.
My first inclination to fixing this issue was to increase the size of the outputted sprite by wrapping the output with rich text tags as follows
<size=150%><voffset=-1em><sprite="PS5_Prompts" sprite="ps5_button_cross"></size></voffset>. While I think this works, it's a pretty brute force way of doing things maybe.
Another way to fix this issue, perhaps a bit more elegantly might be to modify the actual sprite assets as a whole for the given project via the settings somehow.
I'm curious if you might have any thoughts on the best way to handle this 🤔. As for the first method, I can do the work and submit a pr. I was thinking of just adding to the settings something like textFormatter where you enter in something like <size=150%><voffset=-1em>{0}</size></voffset>. Or even openFormatter and closeFormatter.
Hopefully this makes sense, sorry if it's a bit rambly, it's the end of the day but wanted to get your thoughts 😅.

Closing this issue as the above is merged 👍.


embedded_hal errors shouldn't be ignored

While I was working on #26 and similar pr's I found it strange that various embedded_hal errors are just ignored rather than being returned to the caller which seems like the idiomatic thing to do since this is a library.
Example:
https://github.com/rursprung/tb6612fng-rs/blob/82c7c815a49a9e40a0853d095dd8371e6267ed69/src/lib.rs#L237-L238
At first I thought those errors would be encapsulated in DriveError but it seems actually that is only for speed errors so maybe it should be renamed SpeedError.

you're right, i should've probably propagated this upwards! i think this was just a lazy (late-night?) attempt at quickly porting from e-h 0.2 (which had infallible APIs) to 1.0 (which has the Result but in 99.9% of the cases will still be infallible for these actions).
it'd make sense to propagate these errors up to the caller


it may happen that finish log is triggered too early

sometimes it happens, that finish log is triggered before the start log ... some timing issue, harden triggerFinishRound.