Solution skill
Environment variables set to the empty string "" error out
Complete solution
Shows how to fix environment variables set to the empty string "" error out. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
For "}, ] } ` Will result in: ` ╷ │ Error: Error on container create line 417 │ │ with qovery_container.registry-cache-container, │ on qovery.t": use variable interpolation with a non-existent variable to get an empty string anyway, e.g. [spacedub (reporter)]: Workaround: Qovery rejects empty-string env values on container create.
}, ] } ``` Will result in: ``` ╷ │ Error: Error on container create line 417 │ │ with qovery_container.registry-cache-container, │ on qovery.tf line 109, in resourceSteps
- [spacedub (reporter)]: Workaround: Qovery rejects empty-string env values on container create. Use variable interpolation with a non-existent variable to get an empty string anyway, e.g. TLS={{CHEAT}}.
When to use
You are seeing this: [spacedub (reporter)]: Workaround: Qovery rejects empty-string env values on container create. Use this skill when you run into "Environment variables set to the empty string "" error out".
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
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
In the GitHub issue gh:Qovery/terraform-provider-qovery#152 (https://github.com/Qovery/terraform-provider-qovery/issues/152), the problem reported was: Issue Qovery/terraform-provider-qovery#152 (closed, 6 comments): `` resource "qovery_container" "some-container" { environment_variables = [ { key [your value] value = "" }, ] } Will result in: `` ╷ │ Error: Error on container create line 417 │ │ with qoverycontainer.registry-cache-container, │ on qovery.tf line 109, in resource "qoverycontainer" "registry-cache-container": │ 109: resource "qovery_container" "registry-cache-container" { │ │ failed to create container: invalid container upsert request: invalid variable diff request: invalid │ variable upsert request: Key - 'UpsertRequest. The verified resolution was: [spacedub (reporter)]: Workaround: Qovery rejects empty-string env values on container create. Use variable interpolation with a non-existent variable to get an empty string anyway, e.g. TLS={{CHEAT}}.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
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_ihtYUYP9cQ9RfY24_iv-jw" 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">Environment variables set to the empty string "" error out <span>— Vectle</span></a>