magento · jeff-matthews · Feb 8, 2021 · Jan 7, 2021 · Jan 26, 2021 · Jan 27, 2021
diff --git a/src/_data/mde.yml b/src/_data/mde.yml
@@ -361,7 +361,7 @@ extensions:
     name: Product Recommendations
     versions:
       -
-        name: 3.2.2
+        name: 3.2.3
         support:
           2.3.0: supported
           2.3.1: supported
@@ -373,6 +373,18 @@ extensions:
           2.4.0: supported
           2.4.1: supported
           2.4.2: supported
+      -
+        name: 3.2.2
+        support:
+          2.3.0: compatible
+          2.3.1: compatible
+          2.3.2: compatible
+          2.3.3: compatible
+          2.3.4: compatible
+          2.3.5-p1: compatible
+          2.3.6: compatible
+          2.4.0: compatible
+          2.4.1: compatible
       -
         name: 3.10.0
         support:

diff --git a/src/_data/var.yml b/src/_data/var.yml
@@ -21,14 +21,14 @@ 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.8
+mcp-release: 1.0.9
 mcd-package: magento/magento-cloud-docker
 mcd-prod: Magento Cloud Docker
 mcd-release: 1.2.1

diff --git a/src/_data/whats-new.yml b/src/_data/whats-new.yml
@@ -4,9 +4,94 @@ description: This page contains recent changes that we think you'd like to know
   We exclude from this list proofreading, spelling checks, and all minor updates.
 link: "/whats-new.html"
 thread: "/whatsnew-feed.xml"
-updated: Mon Jan 25 15:38:42 2021
+updated: Thu Feb 4 15:51:53 2021
 entries:
-- description: Added the [DateTime library](https://devdocs.magento.com/guides/v2.4/extension-dev-guide/framework/datetime.html)
+- description: Updated the note about [supported PHP versions](https://devdocs.magento.com/guides/v2.3/install-gde/system-requirements.html#php).
+  versions: 2.3.x
+  type: Technical
+  date: February 2, 2021
+  link: https://github.com/magento/devdocs/pull/8613
+  contributor: jeff-matthews
+  profile: https://github.com/jeff-matthews
+- description: New Relic log file names are now stored in the `filePath` field, with
+    full paths to the log file. See [View and analyze log data](https://devdocs.magento.com/cloud/project/new-relic.html#view-and-analyze-log-data),
+    step 4, for querying the logs.
+  versions: 2.4.x
+  type: Major Update
+  date: February 2, 2021
+  link: https://github.com/magento/devdocs/pull/8614
+  contributor: bdenham
+  profile: https://github.com/bdenham
+- description: Cloud Patches 1.0.9 [release notes](https://devdocs.magento.com/cloud/release-notes/mcp-release-notes.html).
+  versions: 2.4.x
+  type: Major Update
+  date: February 1, 2021
+  link: https://github.com/magento/devdocs/pull/8577
+  contributor: bdenham
+  profile: https://github.com/bdenham
+- description: "[Release notes](https://devdocs.magento.com/cloud/release-notes/ece-release-notes.html#v200215)
+    for ECE-Tools 2002.1.5."
+  versions: 2.4.x
+  type: Major Update
+  date: February 1, 2021
+  link: https://github.com/magento/devdocs/pull/8578
+  contributor: bdenham
+  profile: https://github.com/bdenham
+- description: Published [release notes](https://devdocs.magento.com/quality-patches/release-notes.html)
+    for the 1.0.15 Magento Quality Patch (MQP) package release.
+  versions: 2.x
+  type: Major Update
+  date: February 1, 2021
+  link: https://github.com/magento/devdocs/pull/8607
+  contributor: ilima-ebay
+  profile: https://github.com/ilima-ebay
+- description: Added an example use case of the [gallery widget](https://devdocs.magento.com/guides/v2.4/javascript-dev-guide/widgets/widget_gallery.html).
+  versions: 2.3.x, 2.4.x
+  type: Major Update
+  date: January 29, 2021
+  link: https://github.com/magento/devdocs/pull/8556
+  contributor: DashukVolodymyr
+  profile: https://github.com/DashukVolodymyr
+- description: Default disk space for the application and database in cloud templates
+    were updated from 2GB to 5GB.
+  versions: 2.4.x
+  type: Major Update
+  date: January 29, 2021
+  link: https://github.com/magento/devdocs/pull/8588
+  contributor: oshmyheliuk
+  profile: https://github.com/oshmyheliuk
+- description: Added the [Maintainer's Handbook](https://devdocs.magento.com/contributor-guide/maintainer-handbook.html)
+    topic.
+  versions: 2.x
+  type: New Topic
+  date: January 29, 2021
+  link: https://github.com/magento/devdocs/pull/8580
+  contributor: gabrieldagama
+  profile: https://github.com/gabrieldagama
+- description: Added more information about security releases to our [release policy](https://devdocs.magento.com/release/policy/).
+  versions: 2.x
+  type: Major Update
+  date: January 27, 2021
+  link: https://github.com/magento/devdocs/pull/8575
+  contributor: jeff-matthews
+  profile: https://github.com/jeff-matthews
+- description: Updated the [Upgrade Compatibility Tool](https://devdocs.magento.com/upgrade-compatibility-tool/introduction.html)
+    topic with the latest name and acronym changes.
+  versions: ''
+  type: Major Update
+  date: January 26, 2021
+  link: https://github.com/magento/devdocs/pull/8553
+  contributor: danidelcar
+  profile: https://github.com/danidelcar
+- description: Reorganized the [Installation Guide](https://devdocs.magento.com/guides/v2.4/install-gde/install-flow-diagram.html)
+    to improve usability.
+  versions: 2.3.x, 2.4.x
+  type: Major Update
+  date: January 25, 2021
+  link: https://github.com/magento/devdocs/pull/8558
+  contributor: jeff-matthews
+  profile: https://github.com/jeff-matthews
+- description: Added the [DateTime library](https://devdocs.magento.com/guides/v2.3/extension-dev-guide/framework/datetime.html)
     topic to the _PHP Developer Guide_.
   versions: 2.3.x, 2.4.x
   type: New Topic

diff --git a/src/_includes/cache/page-cache-overview.md b/src/_includes/cache/page-cache-overview.md
@@ -21,6 +21,12 @@ We recommend using [Varnish]({{ page.baseurl }}/config-guide/varnish/config-varn
 
 To create an uncacheable page, mark any block on that page as uncacheable in the layout using `cacheable="false"`.
 
+```xml
+<block class="Magento\Customer\Block\Form\Edit" name="customer_edit" template="Magento_Customer::form/edit.phtml" cacheable="false">
+    <container name="form.additional.info" as="form_additional_info"/>
+</block>
+```
+
 Examples of uncacheable pages include the compare products, cart, [checkout](https://glossary.magento.com/checkout) pages, and so on.
 
 [Example]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Paypal/view/frontend/layout/paypal_payflow_returnurl.xml){:target="_blank"}

diff --git a/src/_includes/install/php-versions-2.3.md b/src/_includes/install/php-versions-2.3.md
@@ -1,6 +1,4 @@
 Magento supports PHP 7.3.
 
 {:.bs-callout-warning}
-PHP 7.1 has reached [End of Life](https://www.php.net/supported-versions.php). To maintain PCI compliance, Magento should not be run on unsupported software.
-Installing from GitHub will no longer work with Magento 2.3.4/PHP 7.1.
-The only way to install 2.3.4 with PHP 7.1.x is with Composer.
+PHP 7.1 and 7.2 have reached [End of Life](https://www.php.net/supported-versions.php). To maintain PCI compliance, Magento should not be run on unsupported software. Magento 2.3.x supports PHP 7.3 only and has not been tested with PHP 7.1 or 7.2.
diff --git a/src/cloud/env/variables-build.md b/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_

diff --git a/src/cloud/env/variables-deploy.md b/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`

diff --git a/src/cloud/env/variables-global.md b/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_

diff --git a/src/cloud/project/magento-env-yaml.md b/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.
+```
diff --git a/src/cloud/project/new-relic.md b/src/cloud/project/new-relic.md
@@ -227,7 +227,8 @@ To use the New Relic Logs application:
    {:.bs-callout-tip}
    You can also access the New Relic Logs application from the New Relic ONE home page. See [New Relic ONE core UI components][New Relic One UI].
 
-1. To review infrastructure log data for cloud services, enter the query string `has: "ident"` in the _Find logs where_ field. Then, click **Query logs**.
+1. To review infrastructure log data for cloud services, enter the query string `has: "filePath"` in the _Find logs where_ field. Then, click **Query logs**.
+   The names of the log files are stored in the `filePath` field, with full paths to the log file.
 
    ![Cloud project New Relic service log data]({{ site.baseurl }}/common/images/cloud/cloud_new-relic-log-query-has-ident.png){:width="650px"}
 

diff --git a/src/cloud/project/services-rabbit.md b/src/cloud/project/services-rabbit.md
@@ -125,7 +125,7 @@ For debugging purposes, it is useful to directly connect to a service instance i
    ssh -L 15672:localhost:15672 <project-ID>-<branch-ID>@ssh.us.magentosite.cloud
    ```
 
-1. While the session is open, you can start a RabbitMQ client of your choice from your local workstation, configured to connect to the `localhost:<portnumber>` using the port number, username, and password information from the MAGENTO_CLOUD_RELATIONSHIP variable.
+1. While the session is open, you can start a RabbitMQ client of your choice from your local workstation, configured to connect to the `localhost:<portnumber>` using the port number, username, and password information from the MAGENTO_CLOUD_RELATIONSHIPS variable.
 
 ### Connect from the application {#cloud-rabbitmq-conn-cont}
 

diff --git a/src/cloud/release-notes/ece-release-notes.md b/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

diff --git a/src/cloud/release-notes/mcp-release-notes.md b/src/cloud/release-notes/mcp-release-notes.md
@@ -21,6 +21,14 @@ See [Apply patches]({{site.baseurl}}/cloud/project/project-patch.html) for instr
 
 <!--Add release notes below-->
 
+## v1.0.9
+*Release date: February 1, 2021*<br/>
+
+-  {:.new} **B2B Layered navigation patch**—Fixed the issue that prevented layered navigation from showing all product options when the B2B Shared Catalog was enabled.<!--MCLOUD-6923-->
+-  {:.fix} **Compatibility with PHP 7.4**—Fixed a cloud-patches compatibility issue with PHP 7.4.<!--MCLOUD-7367-->
+-  {:.fix} **Deprecated patches become visible**—Fixed a cloud-patches issue in which deprecated patches become visible in the patches table after applying a replacement patch that contains the entire contents of the deprecated patch. This could happen if you applied a patch that combined several other patches.<!--MC-40626-->
+-  {:.fix} **Silent failures when applying patches**—Fixed a cloud-patches issue in which the `git apply` command silently failed to apply patches in some environments.<!--MC-40529-->
+
 ## v1.0.8
 *Release date: October 14, 2020*<br/>
 

diff --git a/src/common/images/cloud/cloud_new-relic-log-query-has-ident.png b/src/common/images/cloud/cloud_new-relic-log-query-has-ident.png
diff --git a/src/guides/v2.3/coding-standards/code-standard-less.md b/src/guides/v2.3/coding-standards/code-standard-less.md
@@ -720,7 +720,7 @@ Component name must meaningful. It can contain the `primary`, `secondary`, `tert
 
 ### Location
 
-[Theme](https://glossary.magento.com/theme) mixins (except extends) should be located in the `source/utilities` directory.
+[Theme](https://glossary.magento.com/theme) mixins (except extends) should be located in the `web/css/source` directory. For more details, refer to [Css Theme][].
 
 ### Naming
 
@@ -782,3 +782,6 @@ Use single quotes.
 ```css
 @import "source/lib/_lib.less";
 ```
+
+<!-- Link definitions -->
+[Css Theme]: {{ page.baseurl }}/frontend-dev-guide/css-topics/css-themes.html
diff --git a/src/guides/v2.3/coding-standards/technical-vision/webapi.md b/src/guides/v2.3/coding-standards/technical-vision/webapi.md
@@ -82,15 +82,16 @@ Any new design related to Web API must satisfy the following constraints to keep
 1. Web API requests must be processed by custom front controllers with optimized routing to prevent the admin and storefront areas from executing routers.
 1. Web API schema should be strictly typed. (All complex types should eventually be resolved to scalar types.)
 1. Authentication parameters must be passed via headers.
-1. Throttling must be configured by the system integrator. It is not supported by Magento
+1. Throttling must be configured by the system integrator. It is not supported by Magento.
 1. Internal server errors must be masked and never shown to the user in production mode. In developer mode, original exceptions must never be masked and should be displayed along with the related stacktrace.
 1. Pagination must be supported by all list operations.
 
 **GraphQL:**
 
 1. Unlimited nesting should be supported during requests for related entities. (For example, get Order => Order Items => Products => Related Products)
 1. Field filtration must be performed with SQL queries. Do not filter on the application layer after you've fetched all possible fields.
-1. Third-party customizations must be done separately for Service Contracts and for GraphQL
+1. Third-party customizations must be done separately for Service Contracts and for GraphQL.
+1. When possible, classes marked as APIs should be utilized inside GraphQL resolvers.
 1. For modularity purposes, GraphQL configuration must be declared in a separate module. For example, to expose GraphQL for the module `MyModule`, you must create the `schema.graphqls` file in the `MyModuleGraphQl` module.
 1. GraphQL is primarily designed for store-front one-page apps and mobile applications. It supports token and cookie authentication, as well as guest access to public queries
 1. All queries must return the 200 HTTP status code. If an error occurs, return the error in the response body. A 500 status code is allowed when an exception occurs when generating a schema, but not during requests.