[Blueprints] Separate computing the runtime configuration from compiling a Blueprint #2672
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adamziel
changed the base branch from
trunk
to
flatten-stored-runtime-configuration-format
adamziel
added
[Type] Enhancement
adamziel
changed the title
Base automatically changed from
flatten-stored-runtime-configuration-format
to
trunk
September 22, 2025 20:26
…-compiling-a-blueprint
adamziel
deleted the
kickoff-separate-runtime-configuration-from-compiling-a-blueprint
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Replaces
compileBlueprintV1()withresolveRuntimeConfiguration()in all places where the runtime configuration was sourced from a compiled Blueprint. Blueprints v2 are never compiled with TypeScript, hence we need a new concept for sourcing a runtime configuration from a Blueprint.A part of #2586.
Follow-up work
resolveRuntimeConfiguration()still usescompileBlueprintV1()under the hood to keep things easy. Let's fully decouple the two and only compute the runtime configuration without compiling the steps.Testing Instructions (or ideally a Blueprint)
CI