fix: getenv treats an explicitly-empty value as unset #85

Merged
benvin merged 1 commits from benvin/getenv-lookupenv into master 2026-07-02 22:09:09 +10:00
Owner

Fixes #69

Why

getenv returned the fallback whenever os.Getenv was empty, so an intentionally-empty env var could not override a non-empty default.

Changes

  • Use os.LookupEnv to distinguish unset from set-but-empty.

Validation

  • make e2e passes.
Fixes #69 ## Why `getenv` returned the fallback whenever `os.Getenv` was empty, so an intentionally-empty env var could not override a non-empty default. ## Changes - Use `os.LookupEnv` to distinguish unset from set-but-empty. ## Validation - `make e2e` passes.
unkinben added 1 commit 2026-07-02 00:28:42 +10:00
fix: let getenv honour an explicitly-empty env var
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/test Pipeline was successful
ci/woodpecker/pr/build Pipeline was successful
1bed296c35
getenv fell back to the default whenever os.Getenv returned empty, so an
intentionally-empty override was impossible. Use os.LookupEnv to
distinguish unset from empty.

Refs #69
benvin merged commit c39703ed0d into master 2026-07-02 22:09:09 +10:00
benvin deleted branch benvin/getenv-lookupenv 2026-07-02 22:09:10 +10:00
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: unkin/artifactapi#85