4.2.0

What's Changed

• Move Acquia DB backups to cloud v2. by @acidaniel in #218

New Contributors

• @acidaniel made their first contribution in #218

Full Changelog: 4.1.1...4.2.0

Updating to this release

If your project uses a custom version of acquia-get-backup or acquia-load-backup, it will continue to work as it did. However, if you want to use the version directly from the-build, make the following changes:

• Update build.yml to include the correct settings for acquia-get-backup:

# Configuration for targets/acquia.xml
acquia:
  # Local path to store downloaded database backups.
  backups: 'artifacts/backups'
  # Site name as it appears in the Acquia Cloud list of applications.
  site: 'My Site'
  # Database name as it appears in the list of databases for the application.
  database: 'mysite'
  # Environment to pull database backup from (prod, test, or dev).
  env: prod

• Ensure the following settings are correct in the project build.yml:

drupal:
  sites:
    default:
      # OPTIONAL: The Drupal database name defaults to the site's "dir" value.
      database:
        # DDEV's default first database name is "db".
        database: "db"

    # Defaults for all sites; these can be overridden for individual sites.
    _defaults:
      database:
        username: "db"
        password: "db"
        host: "db"

• Add a .env file with the Acquia Cloud API key and secret. See https://github.com/palantirnet/the-build/blob/develop/defaults/install/.env.example
• Remove any targets that override acquia-get-backup or acquia-load-backup from build.xml to allow the target that ships with the-build to be used.