Plans against live state
A plan is a diff against what is actually there, not against a state file that drifted.
Why Foundry
One record of the organization, not five.
Provisioning tools know what you declared. Config tools know what exists. Advisor and cost tools know what it costs and what is risky. Foundry keeps them in one database, so a gate before an apply can use the inventory, and a finding can become a patch.
The argument
What sharing one record buys
Gates that can see the organization
The blast radius gate knows what depends on a resource because the inventory already holds the whole dependency graph.
Findings that lead somewhere
A compliance or advisor finding on a managed resource can become a stack patch that goes through the same planner and approvals.
Cost with its context
Spend is grouped by stack and by the tag taxonomy, next to the findings that explain it.
Honest limits
What it gives up
- AWS only
- No template language, so no sharing of modules: you reuse a stack by copying it
- Inventory is as fresh as the last on-demand scan
- Compliance coverage is partial
Contact
Questions about this tool?
Write to Renkara Media Group and a person will answer.