Known issues in Cloud Platform CD

New environments provision with Cloud Platform default PHP version¶

If a new Cloud Platform environment is provisioned by a CI/CD process, such as Acquia Pipelines or Acquia Code Studio, the new environment is provisioned with the default Cloud Platform PHP version. The new environment does not inherit the PHP settings from the source environment or CI/CD build. For more information on the default PHP version, see default Cloud Platform PHP version.

Workaround: You must set your desired PHP version for the new environment. You can configure the PHP version through the Cloud Platform user interface or the command line.

• Cloud Platform user interface: Modify the PHP version for your application at the environment level using the configuration settings after the new environment is deployed.
• Command line: Change the PHP version with the following Acquia CLI command:

acli app:task-wait "$(acli api:environments:update $TARGET_ENV_ID --lang_version=8.1)"

Pipelines deploys to any environment with a pipelines-build-artifact branch¶

Attempts to use Pipelines to copy databases to a specific environment will succeed even if that branch is deployed to a non-Cloud Platform CD environment, which may have unintended consequences.

Workaround: To prevent this behavior, wrap the pipelines-sync-dbs command in conditional logic, like the following example:

if [ ${PIPELINE_DEPLOY_VCS_PATH} != "pipelines-build-<branch>" ]; then echo "Syncing DB to destination." && pipelines-sync-dbs <databases>; else echo "On the master branch. Skipping DB Sync."; fi

When creating a new CD environment, the post-code-deploy hook is not run¶

When Cloud Platform creates a new Cloud Platform CD environment and deploys code to it, the post-code-deploy cloud hook is not run.

Workaround: To import configuration on a new Cloud Platform CD environment, perform a second deployment to the new environment.

Multiple CD environments created through Pipelines¶

Pipelines runs jobs whenever you create new branches or open pull requests on the connected repository. Most subscribers with GitHub or Bitbucket as the connected repository use a workflow where pull requests are opened from feature branches on forked repositories. It implies that Pipelines jobs do not run against feature branches. However, if you instead create branches on the connected repository and then open pull requests from those feature branches, you will get a Pipelines job for both the feature branch and the pull request. Since each Pipelines job calls pipelines-deploy, you will get a CDE for each job (two CDEs total).

Workaround:

• In the connected repository (GitHub/Bitbucket), modify the webhook settings for Pipelines on the connected repository and disable either the “push” or “pull request webhook depending on your preferred workflow, so that Pipelines only runs jobs for the enabled webhook type.

• In acquia-pipelines.yaml, replace pipelines-deploy with code similar to the following to selectively run pipelines-deploy only on specific types of builds:

  copy

  if [[ ${PIPELINE_DEPLOY_VCS_PATH} == pipelines-build-pr* ]]; then echo "Creating CD environment for PR." && pipelines-deploy; else echo "Not a PR. Skipping CD environment creation."; fi