Fallout-build/Fallout

Environment Variables prepended with `FALLOUT_` don't work.

Open

#457 opened on Jun 30, 2026

View on GitHub
 (4 comments) (0 reactions) (1 assignee)C# (1 fork)github user discovery
buggood first issuetarget/2026target/vCurrent

Repository metrics

Stars
 (43 stars)
PR merge metrics
 (Avg merge 2d 15h) (63 merged PRs in 30d)

Description

Usage Information

10.3.49

Description

Contrary to the information stated in the documentation for Parameters, the code is still looking for NUKE_.

Problem Code: https://github.com/Fallout-build/Fallout/blob/f57634c5636bf5ba4fd0f49eaf0f8360697abcb3/src/Fallout.Build/Execution/ParameterService.cs#L192

I can create a PR later to address this, but I am unsure if it should also remain compatible with NUKE_. LMK what you think.

Reproduction Steps

  1. Create Build Project
  2. Add a string parameter.
  3. Assert in target when parameter is null.
  4. export FALLOUT_MY_PARAMETER_NAME="hello"
  5. Run build, reach assertion.
  6. export NUKE_MY_PARAMETER_NAME="hello"
  7. Run build, no assertion.

Expected Behavior

Environment variables prepended with FALLOUT_ should be used for parameters as per documentation.

Actual Behavior

See Repro.

Regression?

Kind of. Technically?

Known Workarounds

No response

Could you help with a pull-request?

Yes

Contributor guide

Research direction
Change the environment variable prefix from NUKE to FALLOUT in ParameterService.cs line 192, and consider maintaining backward compatibility with NUKE prefix.
Tech stack
csharp
Domain
build system
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#.NET
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75