Skip to content

docs(skill): document the ComputeConfig schema for configs/ - #743

Merged
Aydin-ab merged 2 commits into
mainfrom
docs/compute-config-new-schema
Jun 8, 2026
Merged

docs(skill): document the ComputeConfig schema for configs/#743
Aydin-ab merged 2 commits into
mainfrom
docs/compute-config-new-schema

Conversation

@Aydin-ab

@Aydin-ab Aydin-ab commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Documents the user-facing ComputeConfig schema as the configs/ convention: rewrites schemas/compute-config-schema.yaml, updates the warning in references/conventions.md, and simplifies the create-template compute-config step (workspace config is copied as-is, pruned of defaults — no more schema translation).

Lands after #742.

@Aydin-ab Aydin-ab changed the title docs(skill): document new ComputeConfig schema for configs/ docs(skill): document the ComputeConfig schema for configs/ Jun 3, 2026
@Aydin-ab
Aydin-ab force-pushed the docs/compute-config-new-schema branch from 1436954 to d327629 Compare June 5, 2026 20:31
@Aydin-ab
Aydin-ab marked this pull request as ready for review June 5, 2026 20:38
Aydin-ab added 2 commits June 8, 2026 10:46
configs/ now uses the new user-facing ComputeConfig schema (#742): rewrite the schema reference, flip the legacy warning in conventions, and simplify the create-template compute-config step (workspace config is now copied as-is, pruned of defaults).

Signed-off-by: Aydin Abiar <aydin@anyscale.com>
Per review on #742: from the user perspective there is only one ComputeConfig schema.

Signed-off-by: Aydin Abiar <aydin@anyscale.com>
@Aydin-ab
Aydin-ab force-pushed the docs/compute-config-new-schema branch from d327629 to 4fe2ac3 Compare June 8, 2026 17:46
@Aydin-ab
Aydin-ab merged commit a506b8a into main Jun 8, 2026
4 checks passed
@Aydin-ab
Aydin-ab deleted the docs/compute-config-new-schema branch June 8, 2026 19:08
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.

2 participants