This page describes known issues in Code Studio:
For issues with Cloud Platform CD, see Known issues in Cloud Platform CD.
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)"
If your Drupal application contains deprecated code, changing the PHP version after deployment might cause initial failure notices.
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
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.
Codebases with 1,250 or more git committed files result in a warning and fail the Validate Code job.
The warning does not cause the pipeline to fail.
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.
Pipeline fails due to an unspecified error.
Workaround: Clear the runner caches.
You cannot fully transfer the ownership of a Code Studio project through Cloud UI. You can add a second owner if more than one Code Studio seat exists. The second owner can neither change the role of the original owner nor revoke the seat of the original owner.
To transfer project ownership, contact your Technical Account Manager (TAM) or Acquia Support.