Skip to content

Download Releases

The vdc ingredient-release download command (alias: vdc download) downloads ingredient release packages from VDC to your local system. This command is essential for obtaining dependencies, testing specific versions, and integrating VDC ingredients into your development and CI/CD workflows.


Command Syntax

vdc ingredient-release download [options]
vdc download [options]  # Recommended alias

Required Parameters

  • --project (-p): VDC project name
  • --feed (-f): Feed name within the project
  • --name (-n): Ingredient name
  • --token: Valid VDC authentication token

Optional Parameters

  • --version (-v): Specific version to download (downloads latest if omitted)
  • --target: Local directory for downloaded files
  • --unzip: Extract archives automatically
  • --overwrite: Replace existing files without prompting
  • --verify-checksum: Validate file integrity (recommended)

Options Reference

Option Shortcut Description Required Example
--project <project> -p The project name in VDC Yes --project validation-team
--feed <feed> -f The feed name Yes --feed main
--name <n> -n The ingredient name Yes --name IFWI_NVL
--version <version> -v The ingredient release version No --version 1.0.5
--target <target> Target directory for download No --target ./downloads
--unzip Automatically extract archives No --unzip
--overwrite Overwrite existing files No --overwrite
--verify-checksum Verify file integrity No --verify-checksum
--timeout <seconds> Download timeout in seconds No --timeout 600
--format <json\|yaml> Output format No --format yaml
--verbose Enable detailed logging No --verbose
--token <token> Authentication token Yes --token $VDC_TOKEN

Usage Examples

Basic Downloads

# Download latest version to current directory
vdc download -p validation-team -f main -n IFWI_NVL --token $VDC_TOKEN

# Download specific version
vdc download -p validation-team -f main -n BIOS_DMR -v 1.0.5 --token $VDC_TOKEN

# Download to specific directory
vdc download -p myproject -f main -n firmware-base --target ./downloads --token $VDC_TOKEN

# Download and auto-extract
vdc download -p validation-team -f main -n IFWI_NVL --unzip --target ./extracted --token $VDC_TOKEN

Error Handling and Troubleshooting

Common Error Scenarios

Ingredient/Version Not Found

# Error: Ingredient not found
vdc download -p validation-team -f main -n NONEXISTENT --token $VDC_TOKEN
# Exit code: 1
# Message: "Ingredient 'NONEXISTENT' not found in project 'validation-team', feed 'main'"

# Error: Project not found  
vdc download -p UNKNOWN_PROJECT -f main -n IFWI_NVL --token $VDC_TOKEN
# Exit code: 1
# Message: "Project 'UNKNOWN_PROJECT' not found or access denied"

# Error: Feed not found
vdc download -p validation-team -f UNKNOWN_FEED -n IFWI_NVL --token $VDC_TOKEN
# Exit code: 1
# Message: "Feed 'UNKNOWN_FEED' not found in project 'validation-team'"

# Error: Version not found
vdc download -p validation-team -f main -n IFWI_NVL -v 999.999.999 --token $VDC_TOKEN
# Exit code: 1
# Message: "Version '999.999.999' not found for ingredient 'IFWI_NVL'"

Ingredient Has No Releases

# Error: Ingredient exists but has no releases
vdc download -p validation-team -f main -n EMPTY_INGREDIENT --token $VDC_TOKEN
# Exit code: 
# Message: "Ingredient 'EMPTY_INGREDIENT' has no releases available"

Ingredient Has No Package Files

# Error: Ingredient has releases but no downloadable packages
vdc download -p validation-team -f main -n METADATA_ONLY --token $VDC_TOKEN
# Exit code: 
# Message: "Ingredient 'METADATA_ONLY' has no package files to download"

Quick Troubleshooting Guide

Error Message Cause Solution
"Ingredient 'X' not found" Wrong ingredient name Check spelling
"Project 'X' not found" Wrong project name Verify project name
"Feed 'X' not found" Wrong feed name Check available feeds in project
"Version 'X' not found" Specific version doesn't exist Use vdc ingredient get to see available versions
"Ingredient has no releases" No releases published yet Wait for releases or contact ingredient owner
"Ingredient has no package files" Metadata-only ingredient Use vdc ingredient-release get for metadata
### Debugging Commands
# Check if ingredient exists
vdc ingredient get -p PROJECT -f FEED -n INGREDIENT --token $VDC_TOKEN

# List available releases
vdc ingredient get -p PROJECT -f FEED -n INGREDIENT --format yaml --token $VDC_TOKEN

# Get specific release details
vdc ingredient-release get -p PROJECT -f FEED -n INGREDIENT -v VERSION --token $VDC_TOKEN

# Test with verbose logging
vdc download -p PROJECT -f FEED -n INGREDIENT --verbose --dry-run --token $VDC_TOKEN

Need Other Operations?

Want Advanced Usage?