Unable to set secrets on a job about terraform-provider-qovery HOT 5 CLOSED

@benjaminch https://gist.github.com/anthonymayer/fd54ad43a2cf100680dff536db1fabc4 here's the state and the terraform code that sets it up is mostly below. it's a little bit nested, but here are the relevant parts

resource "qovery_job" "this" {
  # Required
  environment_id = var.environment_id
  name           = var.name

  # Optional
  cpu    = var.cpu
  memory = var.memory
  environment_variables = [
    for envKey, envValue in var.environment_variables : {
      key   = envKey
      value = envValue
    }
  ]

  secrets = [
    for secKey, secValue in var.secrets : {
      key   = secKey
      value = secValue
    }
  ]

  schedule = var.schedule

  source = {
    docker = {
      dockerfile_path = var.dockerfile_path
      git_repository = {
        url       = var.url
        branch    = var.branch
        root_path = var.root_path
      }
    }
  }

  healthchecks = {  }
}

var.secrets gets set to jsondecode(data.aws_secretsmanager_secret_version.insurance_service_secrets.secret_string)
which comes from

data "aws_secretsmanager_secret_version" "insurance_service_secrets" {
  secret_id = "SECRETS_ID_REDACTED"
}

we do the exact same thing with aws_secretsmanager_secret_version and the loop to set the secrets for qovery_application and it works fine there

from terraform-provider-qovery.

@benjaminch I believe I figured out what the cause of the problem is. I have some secrets I'm trying to set with an empty value. This isn't a problem for qovery_application though, but it also fails on qovery_environment. Which behavior should it be? It would be great to support empty values, but most important would be consistent behavior between the resource types IMO.

from terraform-provider-qovery.

Hello @anthonymayer :)
Yes you're right, it should be allowed to set an empty value.
We're currently working on enriching the variables by adding alias & overrides support. The fix for this issue will be embedded too.
I'll tell you when it's done

from terraform-provider-qovery.

Hey @anthonymayer !
Thanks for reporting :)

Do you mind sharing your job terraform setup (remove sensible content)?

Thanks !

from terraform-provider-qovery.

Hello @anthonymayer,
We just released the v0.18.5 that should fix your issue.

from terraform-provider-qovery.