Skip to content

docs: reference module outputs from project config with << … >> templates - #75

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1788408180-cross-module-output-refs
Open

docs: reference module outputs from project config with << … >> templates#75
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1788408180-cross-module-output-refs

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents cross-module output references for the project config file (landing in flightcontrol via ravionhq/flightcontrol#7141–#7148). Adds a "Reference module outputs" section to config-as-code/project-config-file.mdx:

  • << modules.<m>.output.<key> >> / environments.<e>.modules.<m>… / projects.<p>.environments.<e>.modules.<m>… address forms, keyed by givenId
  • behaviour: template text round-trips through pull/apply unchanged; apply orders producers before consumers and rejects cycles; unapplied producers leave the reference pending; producer changes don't auto-rerun consumers (marked stale); references bind to the instance and surface PRODUCER_RENAMED on givenId reuse; delete guards; sensitive outputs not exposed; \<< escape
  • one line on how the app renders a templated input

Should merge after the flightcontrol PR stack ships.

Link to Devin session: https://app.devin.ai/sessions/88946e703fda4c609e13c67fbbd7d7ca
Open in Devin Desktop: https://app.devin.ai/desktop/session/88946e703fda4c609e13c67fbbd7d7ca?variant=devin
Requested by: @flybayer

Greptile Summary

Documents the new project-config syntax and lifecycle semantics for referencing outputs across module, environment, and project boundaries.

  • Adds relative and fully qualified output-reference address forms keyed by givenId.
  • Explains apply ordering, pending and stale references, rename and deletion behavior, sensitive outputs, escaping, and app rendering.

Confidence Score: 5/5

The documentation change appears safe to merge once the referenced flightcontrol implementation has shipped as the PR description requires.

The added MDX is structurally consistent with existing documentation, and no available repository evidence establishes that its newly documented project-config contract is inaccurate.

Important Files Changed

Filename Overview
config-as-code/project-config-file.mdx Adds a focused reference section for cross-module output templates; no concrete repository-supported defect was established.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Config[Project config template] --> Resolve[Resolve producer address]
  Resolve --> Producer[Producer module stack]
  Producer --> Output[Stack output]
  Output --> Consumer[Consumer module input]
  Producer -->|output changes| Stale[Consumer marked stale]
  Stale -->|next stack run| Consumer
Loading

Reviews (1): Last reviewed commit: "docs: reference module outputs from proj..." | Re-trigger Greptile

Co-Authored-By: brandon <brandon@flightcontrol.dev>
@mintlify

mintlify Bot commented Sep 3, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
Ravion 🟢 Ready View Preview Sep 3, 2026, 4:04 AM

@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant