Working on a multi-developer Foundry application and hitting a wall with environment management. Coming from a traditional software background, I'm used to clear dev → staging → prod promotion pipelines, but Foundry's model doesn't seem to map cleanly onto that.
Specifically, the pain points I'm running into:
- Multiple developers need to branch, develop, and test without touching live/prod application.
- No obvious way to promote a "dev" state of an application (Workshop apps, transforms, ontology config) into a "prod" environment cleanly
- Branching in Foundry works if you want a simple feature branch off main, but unable to branch off the feature branch or have live data connection on the branches
I've looked at using separate resource containers and project structures to simulate environments, but it feels like a workaround rather than a first-class pattern that won't slow down development.
**Has anyone cracked this?** Curious what patterns teams are actually using in production engagements — especially on larger programs with multiple devs and real data sensitivity requirements. Are there Foundry-native features I'm missing, or is this genuinely a gap that requires org-level workarounds?