Known issues in Code Studio | Code Studio | Acquia Product Documentation

This page describes known issues in Code Studio:

For issues with Cloud Platform CD, see 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)"
                    

Note

If your Drupal application contains deprecated code, changing the PHP version after deployment might cause initial failure notices.

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.

Note

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.

Unspecified error ¶

Pipeline fails due to an unspecified error.

Workaround: Clear the runner caches.

Unable to transfer project ownership ¶

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.

Deploy Drupal job fails for Federated Authentication projects ¶

The Deploy Drupal job fails with the following error:

Run `acli login` to authenticate via API token and then try again.

For information about the known issue related to Federated Authentication, see Federated Authentication requires a workaround.

Workaround: Add the AH_ORGANIZATION_UUID environment variable to your Code Studio project through the CI/CD variables UI. If the variable is added to the .gitlab-ci.yml file, it might not work as expected. For more information, see Adding environment variables.

Note

To find your organization UUID:

Access Acquia Cloud organizations.
Select your organization.
Retrieve the organization UUID from the URL: https://cloud.acquia.com/a/organizations/<organization-UUID>.

The Code Studio branch URL in the Cloud Platform user interface is incorrect ¶

The Code Studio branch URL that appears next to each environment in the Cloud Platform user interface contains -codestudio-build as an additional string. Therefore, when you click the URL, the system displays a 404 error.

Newly created on-demand environments do not sync with Cloud Platform databases ¶

Newly created on-demand environments must sync with Cloud Platform databases if you set all the environment variables to the correct values. For example:

Environment variable	Value
`ACQUIA_TASKS_SETUP_DRUPAL`	`true`
`ACQUIA_TASKS_SETUP_DRUPAL_CONFIG_IMPORT`	`true`
`ACQUIA_TASKS_SETUP_DRUPAL_STRATEGY`	`sync`
`ACQUIA_CLOUD_SOURCE_ENVIRONMENT_ID`	<DEV_ENV_ID>

However, Code Studio creates an on-demand environment with a new database instead of using the copied Cloud Platform database.

Artifact does not include front-end build assets ¶

Code Studio runs acli push:artifact to deploy build artifacts. The artifact does not include front-end build assets because the .gitignore file ignores them.

Workaround: Complete the following steps:

To override the .gitignore file and commit the files:
1. In the composer.json file, locate the extra key.
2. In the installer-paths key, add an entry with the path to the files that are not present in the artifact.
Add post-install-cmd to your composer.json file. For more information, see Building front-end dependencies.

Unable to configure merge request approval rules ¶

You cannot configure merge request approval rules in your Code Studio account.

Code Studio creates CDEs for all branches¶

Code Studio creates CDEs on non-protected branches and tags even if the ACQUIA_JOBS_CREATE_CDE environment variable is configured only for protected branches and tags.