push-to-registry

Push to HCP Packer Registry

Configure Packer templates to push build metadata to HCP Packer registry.

Reference: HCP Packer Registry

Note: HCP Packer is free for basic use. Builds push metadata only (not actual images), adding minimal overhead (<1 minute).

Basic Registry Configuration

packer {
  required_version = ">= 1.7.7"
}
 
variable

Authentication

Set environment variables before building:

Create HCP Service Principal

1. Navigate to HCP → Access Control (IAM)
2. Create Service Principal
3. Grant "Contributor" role on project
4. Generate client secret
5. Save client ID and secret

Registry Configuration Options

bucket_name (required)

The image identifier. Must stay consistent across builds!

bucket_labels (optional)

Metadata at bucket level. Updates with each build.

build_labels (optional)

Metadata for each iteration. Immutable after build completes.

CI/CD Integration

GitHub Actions

Querying in Terraform

Common Issues

Authentication Failed

• Verify HCP_CLIENT_ID and HCP_CLIENT_SECRET
• Ensure service principal has Contributor role
• Check organization and project IDs

Bucket Name Mismatch

• Keep bucket_name consistent across builds
• Don't include timestamps in bucket_name
• Creates new bucket if name changes

Build Fails

• Packer fails immediately if can't push metadata
• Prevents drift between artifacts and registry
• Check network connectivity to HCP API

Best Practices

• Consistent bucket names - Never change for same image type
• Meaningful labels - Use for versions, teams, compliance
• CI/CD automation - Automate builds and registry pushes
• Immutable build labels - Put changing data (git SHA, date) in build_labels

References

• HCP Packer Documentation
• hcp_packer_registry Block
• HCP Terraform Provider