Expand description
rigg-core - Core types and logic for Azure AI Search and Microsoft Foundry configuration management
This crate provides:
- Resource trait definitions and models (Search and Foundry)
- Workspace and project model
- JSON normalization
- Constraint validation
Re-exports§
pub use resources::ResourceKind;pub use service::ServiceDomain;
Modules§
- binding
- Binding values, implicit
search/foundrybindings, and the per-environment resolution cache. - graph
- Reference-graph ordering for push and delete.
- identity
- The identity graph (spec §3): which service-identity roles does this configuration require, on which scopes, and what settings must hold?
- infra
- Infrastructure references: recognizing, rewriting, and classifying the
values named by the registry’s
crate::registry::InfraReftable. - migrate
- Knowledge-source migration transforms: convert an indexed knowledge
source (azureBlob, azureSql, oneLake, …) with an Azure-generated
pipeline into the explicit
searchIndexshape plus first-class data-source/index/skillset/indexer definitions. - normalize
- JSON normalization for consistent Git diffs
- openapi
- Minimal OpenAPI 3.x model for validating custom WebApiSkill contracts
(spec §9). Rigg does not validate the full OpenAPI grammar — only what a
skillset needs: the paths, and the
values[].dataproperty names of the request and response envelopes. - promote
- Translating one environment’s resource documents into another’s —
the engine behind
rigg promote(specdocs/superpowers/specs/2026-09-09-promote-v2-design.md§2). - registry
- Declarative per-kind metadata registry.
- resources
- Resource kind definitions. Per-kind metadata lives in
crate::registry. - scaffold
- Resource scaffolding: identity-first starter definitions for every kind.
- schema
- Pinned-version schema fixtures (property names per OpenAPI definition): the registry is checked against them, and pull/adopt report fields Azure returns that the pinned version does not know (an API-drift canary).
- service
- Service domain definitions for multi-provider support
- sidecar
$filesidecar handling.- store
- Project-scoped resource file store and sync-state classification.
- workspace
- Workspace and project model.