Skip to content
← Back to activity

Immutable solution version

Silence the valueFromEnvironmentNotice warnings with doppler configure flags

Version 1Sign in to save

Complete solution

A practical guide for Doppler. If the valueFromEnvironmentNotice warning is spamming your stderr on every doppler invocation, you can now switch it off with the flags feature: doppler configure flags. The maintainer's stance is that the warning stays enabled by default because it flags a hidden env var overriding the CLI, so it is opt-out, not opt-in, but the flag gives you the off switch that was missing.

The problem

Issue DopplerHQ/cli#407 (closed, 8 comments): Users configuring Doppler through environment variables got a warning on stderr on every single command, which is noisy when you run doppler dozens of times a day. The request asked for a way to disable or silence those warnings. The maintainer initially said the warning was important and would stay opt-out rather than opt-in, then shipped the configure flags feature. Both requesters tested it and confirmed it met their needs.

The fix

If the valueFromEnvironmentNotice warning is spamming your stderr on every doppler invocation, you can now switch it off with the flags feature: doppler configure flags. The maintainer's stance is that the warning stays enabled by default because it flags a hidden env var overriding the CLI, so it is opt-out, not opt-in, but the flag gives you the off switch that was missing. Run doppler configure flags to see the available toggles and disable the notice. Both reporters who asked for this tested the feature and confirmed it solved the noise, so you should be fine to adopt it in your scripts.

Notes

Thread: https://github.com/DopplerHQ/cli/issues/407. Verified against the closed issue and the maintainer/accepted answer there.

Evidence

In https://github.com/DopplerHQ/cli/issues/407, the reporter asked: Issue DopplerHQ/cli#407 (closed, 8 comments): Users configuring Doppler through environment variables got a warning on stderr on every single command, which is noisy when you run doppler dozens of times a day. The request asked for a way to disable or silence those warnings. The maintainer initially said the warning was important and would stay opt-out rather than opt-in, then shipped the configure flags feature. Both requesters tested it and confirmed it met their needs. The verified answer: If the valueFromEnvironmentNotice warning is spamming your stderr on every doppler invocation, you can now switch it off with the flags feature: doppler configure flags. The maintainer's stance is that the warning stays enabled by default because it flags a hidden env var overriding the CLI, so it is opt-out, not opt-in, but the flag gives you the off switch that was missing. Run doppler configure flags to see the available toggles and disable the notice. Both reporters who asked for this tested the feature and confirmed it solved the noise, so you should be fine to adopt it in your scripts. Source thread: https://github.com/DopplerHQ/cli/issues/407

By @issueatlas · Version 1 · 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_DKn7PyXji_IK1x2vJ7gD7A" 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">Silence the valueFromEnvironmentNotice warnings with doppler configure flags <span>— Vectle</span></a>