By rajeshreeputra on
Change record status: 
Published (View all published change records)
Project: 
Acquia DAM
Introduced in branch: 
1.1.x
Introduced in version: 
1.1.5
Issue links: 
https://www.drupal.org/node/3540159
Description: 

What's New

A new Drush command acquia-dam:update-assets has been added to programmatically check for updates of assets from Acquia DAM. This eliminates the need to manually click "Check for update" on individual media items or wait for cron to queue updates.

New Drush command:

drush acquia-dam:update-assets

What This Solves

Before: Asset version updates (finalized version changes) required either:

  • Manually clicking "Check for Update" on each media item
  • Waiting for the next cron run to queue updates
  • No programmatic way to trigger version checks on demand

After: Run the Drush command to immediately check all DAM assets for version updates and queue them for synchronization.

How to Use

Check for asset updates:

drush acquia-dam:update-assets

This command will:

  • Query all media items using Acquia DAM sources
  • Check each asset against Acquia DAM for finalized version changes and other updates
  • Queue any updated assets into the acquia_dam_media_item_update queue
  • Processes the queue

Recommended Workflow

Option 1: Manual updates when needed

# Check for updates and process queue
drush acquia-dam:update-assets

Option 2: Automated via cron (recommended)

# Add to crontab for regular checks (e.g., every hour)
0 * * * * drush acquia-dam:update-assets

Performance Considerations

First run warning: The initial execution can be resource-intensive if you have many assets with finalized version changes. The command queries the Acquia DAM API for each asset to compare versions.
After regular use: Subsequent runs are faster since version changes are less frequent once assets are synchronized.
Best practice: Run this command regularly (hourly or daily) so version changes are caught incrementally rather than in large batches.

Use Cases

  • Scheduled version checks - Automate version updates via cron
  • On-demand updates - Manually trigger updates after known DAM changes
  • Post-deployment - Check for updates after site deployments
  • Testing - Verify asset synchronization without waiting for cron

Benefits

✅ Programmatic control - Trigger updates on demand without manual clicking
✅ Automation-friendly - Integrate into cron jobs or deployment scripts
✅ Faster updates - No need to wait for the next cron run
✅ Better control - Run updates when it makes sense for your workflow

Impacts: 
Site builders, administrators, editors