ECE tools 2002.1.5 Release

src/_data/var.yml

@@ -21,11 +21,11 @@ mbi: Magento Business Intelligence
 # Cloud product name variables
 
 ece: Magento Commerce Cloud
-ece-release-date: November 19, 2020
+ece-release-date: Feb 1, 2021
 csuite: Magento Commerce Cloud Suite
 ct: ece-tools
 ct-repo: magento/ece-tools
-ct-release: 2002.1.4
+ct-release: 2002.1.5
 mcp-prod: Magento Cloud Patches
 mcp-package: magento/magento-cloud-patches
 mcp-release: 1.0.9

src/cloud/env/variables-build.md

@@ -86,6 +86,21 @@ stage:
     SCD_COMPRESSION_TIMEOUT: 800
 ```
 
+### `SCD_NO_PARENT`
+
+-  **Default**—`false`
+-  **Version**—Magento 2.4.2 and later
+
+Set to `true` to prevent generating static content for parent themes during the build phase.
+
+We recommend setting `SCD_NO_PARENT: false` during the build phase so that generating static content for the parent themes does not impact site deployment or cause unnecessary site downtime. See [Static content deployment]({{site.baseurl}}/cloud/deploy/static-content-deployment.html).
+
+```yaml
+stage:
+  build:
+    SCD_NO_PARENT: false
+```
+
 ### `SCD_MATRIX`
 
 -  **Default**—_Not set_

src/cloud/env/variables-deploy.md

@@ -4,7 +4,7 @@ title: Deploy variables
 functional_areas:
   - Cloud
   - Configuration
-redirect_from: 
+redirect_from:
   - /cloud/trouble/message-queues.html
 ---
 
@@ -425,6 +425,26 @@ You must have a Redis service configured in the `.magento.app.yaml` file and in
 
 The read-only connection is not available for use in the Integration environment or if you use the [`CACHE_CONFIGURATION` variable](#cache_configuration).
 
+### `REMOTE_STORAGE`
+
+-  **Default**—_Not set_
+-  **Version**—Magento 2.4.2 and later
+
+Configure a _storage adapter_ to store media files in a persistent, remote storage container using a storage service, such as AWS S3. Use the remote storage option to improve performance on Cloud projects with complex, multi-server configurations that must share resources.
+
+```yaml
+stage:
+  deploy:
+    REMOTE_STORAGE:
+      driver: aws-s3 # Required
+      prefix: cloud # Optional
+      config:
+        bucket: my-bucket # Required
+        region: my-region # Required
+        key: my-key # Optional
+        secret: my-secret-key # Optional
+```
+
 ### `RESOURCE_CONFIGURATION`
 
 -  **Default**—Not set
@@ -517,6 +537,19 @@ stage:
 
 {% include cloud/note-increase-scd-max-execution-time-variable.md%}
 
+### `SCD_NO_PARENT`
+
+-  **Default**—`false`
+-  **Version**—Magento 2.4.2 and later
+
+On the deploy phase, we recommend setting `SCD_NO_PARENT: true` so that the generation of static content for parent themes does not occur during the deploy phase. This setting minimizes deployment time and prevents site downtime that can occur if the static content build fails during the deployment. See [Static content deployment]({{site.baseurl}}/cloud/deploy/static-content-deployment.html).
+
+```yaml
+stage:
+  deploy:
+    SCD_NO_PARENT: true
+```
+
 ### `SCD_STRATEGY`
 
 -  **Default**—`quick`

src/cloud/env/variables-global.md

@@ -75,6 +75,19 @@ stage:
 
 {% include cloud/note-increase-scd-max-execution-time-variable.md%}
 
+### `SCD_NO_PARENT`
+
+-  **Default**—_Not set_
+-  **Version**—Magento 2.4.2 and later
+
+Set to `true` to prevent generating static content for parent themes during the build and deployment phases. When this option is set to `true`, less static content is generated, which improves your overall build and deployment times.
+
+```yaml
+stage:
+  global:
+    SCD_NO_PARENT: true
+```
+
 ### `SCD_USE_BALER`
 
 -  **Default**—_Not set_

src/cloud/project/magento-env-yaml.md

@@ -112,3 +112,20 @@ stage:
   deploy:
     CLEAN_STATIC_FILES: false
 ```
+
+## Validate configuration file
+
+Use the following CLI command to validate the `.magento.env.yaml` configuration file before pushing changes to the remote Cloud environment.
+
+```bash
+php ./vendor/bin/ece-tools cloud:config:validate
+```
+
+The following sample response provides a list of items to correct:
+
+```terminal
+Environment configuration is not valid. Correct the following items in your .magento.env.yaml file:
+The SCD_THREADS variable contains an invalid value of type string. Use the following type: integer.
+The SCD_STRATEGY variable contains an invalid value fast. Use one of the available value options: compact, quick, standard.
+The NOT_EXIST_OPTION variable is not allowed in configuration.
+```

src/cloud/release-notes/ece-release-notes.md

@@ -17,9 +17,32 @@ The `{{site.data.var.ct}}` package uses the following release versioning sequenc
 {:.bs-callout-info}
 See [Upgrades and patches]({{ site.baseurl }}/cloud/project/project-upgrade-parent.html) for information about updating to the latest release of the `{{site.data.var.ct}}` package.
 
-## v2002.1.4
+## v2002.1.5
 *Release date: {{ site.data.var.ece-release-date }}*<br/>
 
+-  {:.new}**Remote storage**—Added the [`REMOTE_STORAGE`]({{site.baseurl}}/cloud/env/variables-deploy.html#remote_storage) environment variable to enable Cloud Projects for remote storage of media files using a storage service, such as AWS S3.<!--MCLOUD-7153-->
+
+-  {:.new}**New cloud:config:validate command**—Added command `php vendor/bin/ece-tools cloud:config:validate` to validate the `.magento.env.yaml` configuration before pushing changes to the remote Cloud environment.<!--MCLOUD-7120-->
+
+-  {:.new}**Flushing the opcache**—Added support for the `opcache.enable_cli` PHP option to flush the OPcache before running the deploy hook. This configuration resets the cache configuration to ensure that the current configuration settings are applied on each deployment.<!--MCLOUD-7015-->
+
+-  {:.new}**Validation of Aurora DB**—Updated the database service validation so that it is compatible with the Aurora database.<!--MCLOUD-7269-->
+
+-  {:.new}**New SCD_NO_PARENT environment variable**—Added the `SCD_NO_PARENT` environment variable (for Magento >=2.4.2) to manage the generation of static content for parent themes.<!--MCLOUD-7284-->
+
+-  {:.fix}**Memory limits and commands**—Fixed an issue where `php vendor/bin/ece-tools` commands would not work if the size of the `cloud.log` file exceeded the PHP memory_limit. Instead of reading the entire `cloud.log` file into memory, we now only read a smaller subset of data from the log file.<!--MCLOUD-7275--><!--MCLOUD-7400-->
+
+-  {:.fix}**Custom database connections**—Fixed a `.magento.env.yaml` configuration issue in which custom database connections defined for `DATABASE_CONFIGURATION` were not used. The connection settings were not being added to `app/etc/env.php`.<!--MCLOUD-7426-->
+
+-  {:.fix}**Empty error logs**—Fixed an issue that caused deployments to fail if the `cloud.error.log` was empty.<!--MCLOUD-7296-->
+
+-  {:.fix}**MariaDB 10.3 validation**—Fixed validation of MariaDB 10.3 for Magento 2.3.6-p1.<!--MCLOUD-7416-->
+
+-  {:.fix}**Cache:flush logging**—Improved log entries to indicate the start and finish of the `cache:flush` step.<!--MCLOUD-7503-->
+
+## v2002.1.4
+*Release date: November 19, 2020*<br/>
+
 -  {:.fix}Fixed an issue that caused deployment failure when the search engine specified in the `SEARCH_CONFIGURATION` environment variable is a value other than `elasticsearch`.<!--MCLOUD-7283-->
 
 ## v2002.1.3