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)
- Configuration management
- JSON normalization
- Constraint validation
Re-exports§
pub use config::Config;pub use config::ConfigError;pub use config::EnvironmentConfig;pub use config::FoundryServiceConfig;pub use config::ResolvedEnvironment;pub use config::SearchServiceConfig;pub use config::SyncConfig;pub use resources::ResourceKind;pub use service::ServiceDomain;
Modules§
- config
- Configuration management for rigg
- graph
- Reference-graph ordering for push and delete.
- identity
- Identity-graph extraction: which service-to-service RBAC edges does this workspace’s configuration require? (spec §8.2)
- 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. - 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.
- 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.