docs: name the metamodels each coursework task covers - #124
Merged
Merged
Conversation
Shape
CoverageBaseline:
This pull request changed no covered line. |
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
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.
Part of #56.
What this changes
The coursework README's task table now names the metamodels each task covers: Task 1 defines Project Intent as the source and Resolved Deployment as the target, Task 2 transforms Project Intent, resolved against the Platform document, into Resolved Deployment, and Task 3 generates the Deliverable Set from Resolved Deployment. That matches the scope table in
emf/docs/architecture.md.What is left of #56, and why it is not here
Most of the ticket was overtaken by #101, #102 and #103, which rewrote the proposal around the two implementations.
authexample, checked in CIThe three still needed all live in the Overleaf-mirrored proposal, and the mirror is never hand-edited, so they are an Overleaf edit followed by a re-mirror rather than part of this pull request:
02-solution.texsays release CI applies the resources withkubectl apply -k. Delivery is defined separately from the model (docs/adr/deferred/README.md).02-solution.texlists "the alert catalogue" as platform data. The Platform document carries no rule catalogue (spec/v1/14-platform-intent.md#monitor-cadence).04-generated-code.texsays one Deliverable Set per application and one Kustomize entry point. The six central adapters run once over the composed union and produce one tree for the estate (spec/v1/30-deliverables.md).Verification
npm run lint:links: 186 files clean.npm run lint:meaning: 165 files clean.npm run verifyexit 0: 722 tests, coverage unchanged.