Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/cloud/env/variables-build.md
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,19 @@ stage:
SKIP_SCD: false
```

### `SKIP_COMPOSER_DUMP_AUTOLOAD`

Skip executing of `composer dump-autoload` command.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Skip executing of `composer dump-autoload` command.
Skip execution of `composer dump-autoload` command.

Copy link
Contributor

@meker12 meker12 Oct 7, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggest: Avoid using terms like execute and terminate:

Do not run the composer dump-autoload command.

Why do you need to set this variable? Do you only set it if you are deploying Cloud project using Magento Cloud Docker?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@meker12 Executing composer dump-autoload command causes an error when running some Magento commands such as bin/magento deploy:mode:set production or bin/magento -n setup:upgrade. These commands can be run on writable systems, for example in the magento-cloud-docker test container. So we added a possibility to skip it.
This is a core issue magento/magento2#23251, but I don't know when it will be fixed.


- **Default**— _Not set_
- **Version**—Magento 2.1.4 and later

```yaml
stage:
build:
SKIP_COMPOSER_DUMP_AUTOLOAD: true
```

### `VERBOSE_COMMANDS`

- **Default**—_Not set_
Expand Down