Content Hub Upgrade Console (CHUC) is a console-based tool, which helps Acquia Content Hub 8.x-1.x customers to upgrade to the latest version 2.x. Apart from upgrading, it also provides auditing, troubleshooting and fleet-wide commands to Content Hub customers.
See Evaluating Acquia Content Hub 8.x-1.x deployment before upgrading to Acquia Content Hub 8.x-2.x before proceeding to upgrade to Acquia Content Hub 8.x-2.x.
Important
If you employ Acquia Content Hub 8.x-1.x to syndicate content for re-use across your fleet of sites with multiple sites enabled as either publishers and subscribers, an upgrade is strongly recommended.
If you exclusively use your Acquia Content Hub installation to enable Acquia Personalization, we recommend you do not upgrade to Acquia Content Hub 8.x-2.x. This typically means that Acquia Content Hub is installed on a single site configured as a publisher. Acquia Content Hub 8.x-1.x continues to support and enable Acquia Personalization.
Contact your Acquia account representatives or Acquia support if you need help determining your use of Acquia Content Hub.
Note
To perform a Acquia Content Hub 8.x-1.x to Acquia Content Hub 8.x-2.x upgrade, ensure that you are running the most recent version of Acquia Content Hub, that is, 8.x-1.49 or later. Also, ensure that you are upgrading to Content Hub 8.x-2.21 or later.
Ensure that the environment you are planning to upgrade is currently operational.
For example, stage down production site to the dev environment and ensure that Acquia Content Hub 8.x-1.x is working in the dev environment.
From your local computer, navigate to the location where acquia/contenthub-console is installed and create a platform:
./vendor/bin/commoncli platform:create
This will ask you for credentials to Acquia Cloud or Acquia Cloud Site Factory for any sites you’d like to upgrade. Note that you should add all applications to the platform you create so the upgrade process happens on all of the relevant applications across your Content Hub fleet of sites in the environment specified.
Note
There are three platforms available in Acquia Content Hub: Acquia Cloud, Acquia Cloud multi site, Acquia Cloud Site Factory.
Run the following command to start the upgrade:
./vendor/bin/commoncli ach:upgrade:start @platform_alias
This command will walk you through all of the necessary steps to upgrade to
Acquia Content Hub 8.x-2.x. @platform_alias
should be the alias you
created when running the ./vendor/bin/commoncli platform:create
command.
The following stages represent each step in the process of upgrading. Most stages are performed automatically by the tool outside of the manual deployment step after stage 3.
What does it do?
What if something goes wrong?
Ensure that your platform has been set correctly by running the following command:
/vendor/bin/commoncli platform:describe
If any of the audits find a problem, it is important to fix the issue. Some issues can be fixed by CHUC while others will need to be fixed manually. These are known problems that the Content Hub Console is attempting to prevent prior to the Acquia Content Hub 2.x upgrade.
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
Run the following composer commands on your 8.x-1.x codebase to get the necessary modules installed:
composer remove acquia/content-hub-php
composer remove depcalc
composer remove drupal/acquia_contenthub
composer require drupal/acquia_contenthub:~2
composer require drupal/diff
After running the composer commands above, commit the code to your Acquia-hosted repository and deploy the branch.
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
Contact Acquia Support if there’s a failure to create the scheduled job.
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
What does it do?
What if something goes wrong?
After the package has been added to your application, you can list all commands available by running:
./vendor/bin/commoncli
Here are the two most relevant commands for upgrade:
Create a platform:
./vendor/bin/commoncli platform:create
Start the upgrade:
./vendor/bin/commoncli ach:upgrade:start @platform_alias