Compute identity fingerprints for components
Compute a deterministic identity fingerprint for each selected component.
The fingerprint captures all resolved build inputs (config fields, spec file content, overlay source files, distro context, and Affects commit count). A change to any input produces a different fingerprint.
Use this with 'component diff-identity' to determine which components need rebuilding between two commits.
azldev component identity [flags]
# All components, JSON output for CI
azldev component identity -a -O json > identity.json
# Single component, table output for dev
azldev component identity -p curl
# Components in a group
azldev component identity -g core
-a, --all-components Include all components
-p, --component stringArray Component name pattern
-g, --component-group stringArray Component group name
-h, --help help for identity
-s, --spec-path stringArray Spec path
-y, --accept-all accept all prompts
--color mode output colorization mode {always, auto, never} (default auto)
--config-file stringArray additional TOML config file(s) to merge (may be repeated)
-n, --dry-run dry run only (do not take action)
--network-retries int maximum number of attempts for network operations (minimum 1) (default 3)
--no-default-config disable default configuration
-O, --output-format fmt output format {csv, json, markdown, table} (default table)
--permissive-config do not fail on unknown fields in TOML config files
-C, --project string path to Azure Linux project
-q, --quiet only enable minimal output
-v, --verbose enable verbose output
- azldev component - Manage components