Repository navigation
feat(playground): plan the scenarios as changes to existing infrastructure - #27
Merged
Merged
Conversation
…cture Each family's base plan now reads the existing platform with no changes and its head plan proposes a change against the same state. The Forms, the documentation figures, the tour and the quoted outputs follow the new plans, and documentation downloads follow dev again. The AWS presentation catalog maps its Rules and Concepts to the official AWS Architecture Icons, and five Azure Rules use official Azure icons.
Contributor
Contribution progressSource: Selected validations:
Applicable consumers are synchronized on their development branches and the staging sites. Releases are published from main; the Release row follows them. |
… plans The reference runtime check verifies scripts/fixtures/reference-playground against the current scenario inputs. Regenerate those Forms with the pinned reference runtime 0.1.0-pr.117.1 so they describe the new plans.
Contributor
Author
|
/rootform retry |
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.
Change
The three Playground families now plan a change to existing infrastructure instead of building everything from an empty state. In each family,
baseis the existing platform planned with no changes andheadis the proposed change planned against the same state, so most resources stay in place and the plan proposes a few additions, updates and removals:platformLog Analytics workspace, container insights is replaced, and the legacy blob webhook pipeline is retired. The apps node pool grows to 20 nodes without an architectural change.Plan: 2 to add, 2 to change, 4 to destroy.Plan: 2 to add, 1 to change, 1 to destroy.Plan: 5 to add, 3 to change, 0 to destroy.Terraform produced every plan with the pinned providers and without refresh, against a state built offline from
base, asexamples/playground/README.mddescribes. Credentials that only a cloud API would generate are low-entropy placeholders.The analysis and comparison Forms, the documentation figures and tour, and the documentation that quotes these samples follow the new plans. Documentation downloads follow
devagain.The reference runtime Playground Forms in
scripts/fixtures/reference-playgroundare regenerated from the new plans with the pinned reference runtime0.1.0-pr.117.1.The AWS presentation catalog maps 106 of 108 Rules and its Concepts to official AWS Architecture Icon identities; subnets and security groups keep a neutral symbol. Five Azure Rules move from generic symbols to official Azure icons: node pools, blob containers, storage queues, public IP addresses and virtual network peerings.
Validation
bun run check: 307 tests pass.bun scripts/playground-forms.tswith Rootform 0.2.0: six plan inputs and verified saved-plan pairs; three analysis and three comparison Forms reproduce byte for byte.bun scripts/verify-docs-examples.ts: journey, concept, automation, language, authoring and learning examples pass against the new plans.bun scripts/ci/run.ts dialects policies examples scenarioswith the reference runtime0.1.0-pr.117.1: Dialects, Policies and documented examples pass, and the reference Playground Forms reproduce byte for byte.No changes; head plans report the summaries above.