Struct DiffEngine 

pub struct DiffEngine;

Diff engine for comparing Kubernetes resources

Implementations

impl DiffEngine

pub fn normalize(resource: &mut Value)

Normalize a resource for comparison by removing auto-generated fields

This removes fields that Kubernetes generates automatically and should not be considered when comparing desired vs live state:

• metadata.resourceVersion
• metadata.uid
• metadata.generation
• metadata.creationTimestamp
• metadata.managedFields
• metadata.selfLink
• status (entire section)

pub fn to_comparable_yaml(resource: &Value) -> Result<String>

Convert a resource to normalized YAML string for comparison

This normalizes the resource and converts it to YAML with consistent formatting for reliable comparison.

pub fn diff_yaml(desired: &Value, live: &Value) -> Result<String>

Compare two resources and return a unified diff (kubectl-style)

This generates a unified diff similar to kubectl diff by:

1. Normalizing both resources
2. Converting to YAML
3. Running a line-by-line unified diff algorithm

Returns empty string if resources are equivalent.

pub fn are_equivalent(desired: &Value, live: &Value) -> Result<bool>

Check if two resources are equivalent after normalization

This is a simple equality check after normalization. Use this for determining if resources differ, then use diff_yaml() to show what changed.

pub async fn normalize_with_server( resource: &Value, client: Option<&dyn KubeClient>, ) -> Result<Value>

Normalize a resource with optional server-side normalization

If a client is provided, sends the resource to the server with dry-run to apply server-side defaults. Otherwise, just clones the resource. In both cases, applies client-side normalization to remove metadata fields.

pub async fn diff_yaml_with_server( desired: &Value, live: &Value, client: &dyn KubeClient, ) -> Result<String>

Generate a diff with server-side normalization

Uses server-side apply dry-run to normalize the desired resource, then compares against the live resource (which already has server defaults).

pub async fn are_equivalent_with_server( desired: &Value, live: &Value, client: &dyn KubeClient, ) -> Result<bool>

Check if two resources are equivalent with server-side normalization

Uses server-side apply dry-run to normalize the desired resource, then compares against the live resource.