## TL;DR

This was fixed in provider v0.18.5, so upgrade; as a workaround, avoid empty secret values.

## Steps

1. What was reported:
Issue Qovery/terraform-provider-qovery#271 (closed, 5 comments): │ Error: Error on job update │ failed to update job: invalid job upsert request: invalid secrets diff request: invalid secrets upsert request: Key - 'UpsertRequest.Value' Error:Field validation for 'Value' │ failed on the 'required' tag I'm trying to set secrets on a new `qovery_job`. I'm setting secrets for the job exactly how I'm setting them for a `qovery_application` but it fails. I tried both when creating the job and when that didn't work I created the job with no secrets and tried to add them as a change and I got the exact same error. Setting environment variables works.

2. What works:
If setting secrets on a qovery_job fails validation while qovery_application accepts the same config, check for empty secret values: they were rejected on jobs by a provider bug. This was fixed in provider v0.18.5, so upgrade; as a workaround, avoid empty secret values.

## When to use

You are seeing this: I'm setting secrets for the job exactly how I'm setting them for a qovery\_application but it fails. Use this skill when you run into "Unable to set secrets on a job".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: provider v0.18.5. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
