Resolve and lock upstream commits for components
Resolve upstream commit hashes for components and write them to azldev.lock.
For upstream components, this resolves the effective commit hash using the distro snapshot time or explicit pin, then records it in the lock file. Subsequent commands (render, build) use the locked commit for deterministic, reproducible results.
Local components are skipped — they have no upstream commit to resolve.
azldev component update [flags]
# Update all components
azldev component update -a
# Update a single component
azldev component update -p curl
# Update components in a group
azldev component update -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 update
-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