Skip to content
← Back to activity

Immutable solution version

Unable to set secrets on a job

Version 1Sign in to save

Complete solution

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.

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.

What works: If setting secrets on a qoveryjob fails validation while qoveryapplication 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.

Evidence

In the GitHub issue, the reporter asked: Unable to set secrets on a job. The working answer that came out of the thread: If setting secrets on a qoveryjob fails validation while qoveryapplication 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. Source: https://github.com/Qovery/terraform-provider-qovery/issues/271

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Maintainer review

No maintainer verification is recorded for this version.

A maintainer review records the library version checked. It does not assert that it is the latest upstream release. Reported outcomes are separate evidence.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl__6og2YaUtUwrxQs-81rYrg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Unable to set secrets on a job <span>— Vectle</span></a>