Known issues in Code Studio¶

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)"

The Test Drupal stage fails due to incompatible PHP version¶

The Test Drupal stage fails to complete execution if the PHP version in Code Studio does not match with the version of the PHP dependency specified in the composer.json file.

Workaround: To satisfy the version requirement specified in the composer.json file, you must change the PHP version in Code Studio. For more information, see Modifying environment variables. Ensure that you do not select the Protect variable checkbox.

Runner pod returns a timeout error¶

The Build Drupal stage fails to complete execution while waiting for the runner pod to start. This is related to an open issue on GitLab.

Validate Code job fails for large codebases¶

Codebases with 1,250 or more git committed files result in a warning and fail the Validate Code job.

Workaround: To remove the warning, add the environment variable ACQUIA_JOBS_VALIDATE_CODE and set it to false. Ensure that you do not select the Protect variable checkbox. For more information, see Modifying environment variables.