understanding-saleor-domain

Aligning YAML state across environments requires understanding entity identification rules (slug vs. name), deployment stage dependencies, and schema validation. The Saleor domain rules explain how Products reference ProductTypes, how stages must be sequenced, and how to detect configuration drift between local and remote states using diff comparison.

Saleor uses slug-based, name-based, and singleton patterns to identify entities in YAML configurations. Slug identification is immutable and preferred for cross-reference validation; name-based identification requires careful handling during migrations. Understanding these patterns prevents duplicate detection failures and ensures proper entity resolution during deployment.

Saleor enforces stage dependency sequencing where certain resources—like Products—require existing prerequisite resources like ProductTypes. The deployment pipeline respects these dependencies to prevent validation failures. Stage order determines which entities deploy first, and cross-reference validation ensures all dependencies resolve correctly.

Saleor deployments organize entities into stages with defined ordering and dependency relationships. Each stage can deploy selectively, and dependencies between stages must be satisfied before proceeding. Understanding stage sequencing and selective deployment options prevents configuration conflicts and ensures repeatable, predictable infrastructure updates.

Saleor YAML configurations follow specific schema patterns for entity definition, references, and metadata. Schema synchronization across environments requires validating structure against expected patterns. Knowing the correct YAML structure prevents deployment failures and ensures consistent behavior across local, staging, and production environments.

Configuration drift occurs when local YAML diverges from remote deployment state. Diff and compare logic identifies misaligned entities, missing resources, and broken references. Saleor domain rules help you understand which differences are safe, which require migration, and how to synchronize state without data loss.