Fallout-build / Fallout-build/Fallout

Configuration-provider abstraction: standalone appsettings.json + GitHub/Octopus injectors

Open
#335 0 comments 0 reactions 0 assignees View on GitHub
enhancement RFC target/vNext
Dominant language
C#
Stars
154
Forks
19
Avg merge
1d 22h
Merged PRs (30d)
15

Description

Part of #332.

Channel/target/environment definitions (sibling issue) must resolve through **pluggable configuration providers**:
- **Standalone** — `appsettings.json` supplies values; Fallout drives CD itself, in lieu of any parent system.
- **Injected** — from a parent system: GitHub (Environments/secrets), Octopus Deploy, Azure DevOps.

This is what lets the same build run inside a forge **or** fully self-hosted. Relates to #252 (`[NeverLiteral]` for env-sourced fields) and the secret conventions in #167. RFC the provider contract + precedence/override rules.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.