Unify components and recipes #227
Merged
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.
This PR consolidates the interfaces for recipes and components by having both operate directly on manifests rather than returning services/manifests. This simplifies the architecture and makes the system more composable.
Previously, recipes and components had different interfaces for modifying manifests:
This distinction created unnecessary complexity since both are fundamentally doing the same thing: configuring and adding services to a manifest. The only real difference is that recipes are public CLI entry points while components are internal execution units - but this semantic difference doesn't justify different technical interfaces.