Fallout-build / Fallout-build/Fallout
Stand up Topaz (Azure emulator) as a cheap target for Azure CD primitives
- Dominant language
- C#
- Stars
- 154
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 15
Description
Part of the **Continuous Delivery Vision** ([milestone #8](https://github.com/ChrisonSimtian/Fallout/milestone/8)); tracked under the **CD: Azure Cloud (Topaz)** sub-milestone (#14).
## Idea
Adopt **Topaz** (open-source Azure cloud emulator) as a local, free target so we can build and exercise **Azure-specific CD primitives** without real Azure spend. This is directly motivated by a real workplace need — which makes it a cheap, high-signal proving ground for Fallout's deployment/release orchestration work.
## Why this is a good first Azure CD bet
- **Cheap to iterate** — emulated Azure means no subscription cost or teardown discipline while prototyping.
- **Real demand** — needed at `$work`, so the primitives get validated against an actual use case instead of a hypothetical one.
- **Dogfoodable** — integration tests for Azure CD targets can run against Topaz in CI later.
## Rough scope (shape TBD — this is a tracking/scoping issue, not a spec)
- [ ] Pin the canonical Topaz project/repo + confirm which Azure services it emulates and how faithfully.
- [ ] Document running Topaz locally (container) for dev/test.
- [ ] Prototype Azure-specific CD building blocks against it (e.g. resource/group deployment, storage, app/service deploy — narrow to what `$work` actually needs first).
- [ ] Decide what graduates into a real Fallout CD primitive vs. stays a sample.
- [ ] Wire Topaz as an integration-test target once primitives stabilise.
## Notes
- Long-horizon, no release commitment — lives under the CD vision umbrella.
- Per demand-driven scoping: start from the concrete `$work` use case, not a broad "emulate all of Azure" goal.
Contributor guide
Assessment
This issue has not been assessed yet.