Remote Administration (RA) follows a specific workflow implemented by automation that takes into account subscription-specific preferences. If you are a Remote Administration customer, setting your application update preferences correctly ensures security updates can be smoothly integrated into your workflow.
To review your RA application update preferences, completing the following steps:
Select the application whose RA settings you want to view.
In the left menu, click RA.
Cloud Platform displays the RA update settings in place for your application.
RA customers have several available update methods, and whichever method you select influences subsequent options.
To modify your RA settings (such as changing your update settings or removing RA from your application), complete the following steps:
Go to the Remote Administration settings page for your application.
In the upper right of the page, click the Edit icon.
In the Update process list, click the update method you want to use with your application, from the following list:
Update and Deploy (default): When a security update is required,
Acquia creates a new branch from the branch or tag currently deployed to
production, applies security updates, and pushes the branch to the
repository.
The new branch is then deployed to your RA environment for testing. Acquia notifies you using a ticket that
the secure branch is available for testing. RA can deploy the updates to
production for you, but will not do so without your explicit approval.
Inform only: Acquia informs you of pending updates using a security update notification. No further action is taken without your specific request.
Do not inform: Acquia does not inform you of any pending updates. No further action is taken without your specific request. Select the Do not inform method if your website uses continuous integration (CI).
Depending on your selection in the Update process list, Cloud Platform may display additional fields regarding the implementation details for your selected method.
Update method |
Displayed field |
Description |
Default value |
---|---|---|---|
Update and Deploy |
Pause until |
Enter a date and time to pause RA until that time. After that time, RA will resume its normal schedule. |
not paused |
Update and Deploy |
Update type |
Select from Core and Core and contributed modules to
determine the portions of your application you want to update. |
Core and contributed modules |
Update and Deploy |
Secondary testing environment |
Acquia deploys the initial security update branch to the RA environment. After you approve the branch for tagging and final testing, you can have Acquia place this tag on any environment (other than production) for final testing. A fresh copy of the production database will be copied into this environment as a part of this final, pre-production test. |
|
Update and Deploy |
Deploy on a specific Day/Time |
Enter a date and time for RA to deploy the update tag created and approved during Step 2 of the RA update process. Once you enter the date and time, update the existing RA update ticket so that the deploy can be queued to happen on the specified time. |
No deploy scheduled |
Update and Deploy |
Copy files from production to testing environment |
Acquia strongly recommends you click Yes to ensure accurate and up-to-date tests. |
Yes |
Update and Deploy |
Copy prod database to testing environment |
Acquia strongly recommends you click Yes to ensure accurate and
up-to-date tests. |
Yes |
Update and Deploy |
Merge update tag into development branch |
Determines whether or not to merge the tested security update tag
into your preferred branch after the tag has been deployed to
production. |
Yes |
Update and Deploy |
Merge development branch |
Acquia typically merges updates into |
|
Inform only |
Pause until |
Enter a date and time to pause RA until that time. After that time, RA will resume its normal schedule. |
not paused |
Do not inform |
Does not display any additional preference fields |
Click Save.
RA will now use your selected update settings for your application.