mirror of
https://github.com/hanzoai/o11y-foundry.git
synced 2026-11-03 02:08:34 +00:00
PandeyandGitHub
154abe7629
## Summary - Wires schema-based validation of `casting.yaml` at config load time. Schema is generated from the Go types via `swaggest/jsonschema-go`, embedded as `api/v1alpha1/schema.json`, and validated post-merge with `google/jsonschema-go`. - Adds field-level rules: `required`, `enum`, `pattern` (DNS-1123 name, JSON Pointer paths, OCI image), `minimum`/`minLength`/`minItems` on the relevant fields. `additionalProperties:false` is set on every nested type for the published schema. - Replaces the loose string `Platform` / `Mode` / `Flavor` on `TypeDeployment` with typed enums following the existing `*Kind` pattern. Bad values now fail at unmarshal with a clear "invalid deployment …" message. - Drops `InfrastructureProvider` in favor of `Platform` — the cloud subset (aws, gcp, azure) drives the Terraform IaC pipeline directly. `ResolveProvider` collapses `PlatformECS → PlatformAWS`. - Side cleanups bundled here: typed errors in `internal/errors` with stacktrace capture (used by yamlconfig to wrap validation failures as `TypeInvalidInput`), and removal of the custom pretty slog handler in `internal/instrumentation` in favor of `slog.NewJSONHandler`. ## Test plan - [ ] `make gen-schemas` is idempotent (CI's `schemas` job stays green). - [ ] `go test ./...` passes locally. - [ ] Every committed example casting (`docs/examples/**/casting.yaml`, `docs/standalone/casting.yaml`) loads without error. - [ ] Negative cases at config load: bad `apiVersion`, missing required fields, unknown enum values for `kind` / `mode` / `flavor` / `platform` / patch `op`, non-JSON-Pointer patch paths, negative `replicas`, `shards: 0`, malformed image refs — each fails with a `TypeInvalidInput` error pointing at the offending location. - [ ] `foundryctl forge` against `docs/examples/docker/compose/casting.yaml` still produces the expected pours.