Merge pull request #4 from magento/master

Sync with upstream

Author: snowcore

.imgbotconfig

@@ -0,0 +1,6 @@
+{
+	"ignoredFiles": [
+		"*.svg"
+	],
+	"aggressiveCompression": false
+}

Gemfile.lock

@@ -1,8 +1,8 @@
 GIT
   remote: https://github.com/magento-devdocs/devdocs-theme.git
-  revision: 84a3ed7f0df264a2c2086167efbd7d0545d329c4
+  revision: 5e99a84dd5692d3ee4c1985b9f48824eeede8cfd
   specs:
-    devdocs (4)
+    devdocs (5)
       jekyll (>= 3.3)
 
 GEM
@@ -95,10 +95,9 @@ GEM
     launchy (2.4.3)
       addressable (~> 2.3)
     liquid (4.0.3)
-    listen (3.1.5)
-      rb-fsevent (~> 0.9, >= 0.9.4)
-      rb-inotify (~> 0.9, >= 0.9.7)
-      ruby_dep (~> 1.2)
+    listen (3.2.0)
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
     mdl (0.5.0)
       kramdown (~> 1.12, >= 1.12.0)
       mixlib-cli (~> 1.7, >= 1.7.0)
@@ -124,8 +123,7 @@ GEM
     rb-fsevent (0.10.3)
     rb-inotify (0.10.0)
       ffi (~> 1.0)
-    rouge (3.11.0)
-    ruby_dep (1.5.0)
+    rouge (3.12.0)
     safe_yaml (1.0.5)
     sass (3.7.4)
       sass-listen (~> 4.0.0)

_data/toc/ui-components-guide.yml

@@ -50,6 +50,9 @@ pages:
         - label: DynamicRows component
           url: /ui_comp_guide/components/ui-dynamicrows.html
 
+        - label: DynamicRowsRecord component
+          url: /ui_comp_guide/components/ui-dynamicrows-record.html
+
         - label: Email component
           url: /ui_comp_guide/components/ui-email.html
 

_includes/config/setup-cron_2.3_how-to.md

@@ -43,17 +43,3 @@ content='The `update/cron.php` file exists in [Composer](https://glossary.magent
 
 In [Composer-based installations](https://glossary.magento.com/composer), Magento creates the `update/` directory when you run `composer create-project`. Running `composer install` does not create the `update/` directory (if it did not exist before). See [Recreate the Magento updater](https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#recreate-magento-updater).'
 %}
-
-Starting from Magento 2.3.4 mentioned crons have been grouped to `default` (`cron:run`, `update/cron.php`, `setup:cron:run` crons) and `non-optional` (`cron:run` cron only) groups.
-
-Use `-d` or `--non-optional` to install non-optional CRON job:
-
-```bash
-bin/magento cron:install --non-optional
-```
-
-```terminal
-#~ MAGENTO START
-* * * * * /usr/bin/php /var/www/html/magento2/bin/magento cron:run | grep -v Ran jobs by schedule >> /var/www/html/magento2/var/log/magento.cron.log
-#~ MAGENTO END
-```

_includes/graphql/customizable-option-input.md

@@ -1,4 +1,4 @@
 Attribute |  Data Type | Description
 --- | --- | ---
 `id` | Int! | A unique ID assigned to the customizable option
-`value_string` | String! | A value assigned to the the customizable option
+`value_string` | String! | A value assigned to the customizable option

_includes/install/auth-tokens-get.md

@@ -21,7 +21,9 @@ You can also disable or delete authentication keys. For example, you can disable
 *  To enable a previously disabled key: Click **Enable**.
 *  To delete keys: Click **Delete**.
 
-You cannot delete or disable keys you created by signing in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}. To manage those keys:
+### Manage SSH access token
+
+To download Magento releases using SSH, you must generate a Downloads Access Token. To generate a token:
 
 1. Log in to your [magento.com account](https://www.magentocommerce.com/products/customer/account/login){:target="_blank"}.
 1. Click **My Account** at the top of the page.
@@ -30,3 +32,11 @@ You cannot delete or disable keys you created by signing in to your [magento.com
    ![Access your keys]({{ site.baseurl }}/common/images/connect_keys1.png){:width="200px"}
 
 1. Click **Generate new token** to replace and disable an existing token.
+
+You must use your MAGEID plus your token to download a release. Your MAGEID is displayed at the top-left of your account page.
+
+For example:
+
+```bash
+curl -k https://MAGEID:[email protected]/products/downloads/info/help
+```

common/images/graphql/authorize-net.svg

@@ -216,7 +216,7 @@ Unassigning a product does not remove it from its category or categories.
 
 `true`, indicating the operation was successful
 
-### List the shared catalog categories
+### List the shared catalog products
 
 The `GET` call returns an array of SKUs.
 

common/images/graphql/braintree-vault.svg

@@ -220,7 +220,7 @@ Fastly sets a 180 second-timeout for HTTPS requests to the Magento Admin, so you
 
 1. In the *Fastly Configuration* section, expand **Advanced**.
 
-1. Set the **Admin path timeout** value in seconds. This value cannot be more than one hour (3600 seconds).
+1. Set the **Admin path timeout** value in seconds. This value cannot be more than 10 minutes (600 seconds).
 
 1. Click **Save Config** at the top of the page.
 

common/images/graphql/braintree.svg

@@ -18,10 +18,10 @@ You can [set up log-based Slack and email notifications][slacklog] when configur
 
 ## Viewing logs
 
-There are three ways to view logs: file system, project web UI, or magento-cloud CLI.
+There are three ways to view logs: file system, project web UI, or the `magento-cloud` CLI.
 
--  **Log directories**—The `var/log` directory contains logs for all environments. You must use an SSH connection to access the `var/log` directory in the remote server environment.
--  **Project web UI**—You can see build and post-deploy log information in the environment messages list.
+-  **Log directories**—The `/var/log` system directory contains logs for all environments. The `var/log/` Magento directory contains app-specific logs unique to a particular environment. You must use an SSH connection to access logs in a remote server environment. These directories are not shared between nodes in a cluster.
+-  **Project web UI**—You can see build and post-deploy log information in the environment _messages_ list.
 -  **Magento Cloud CLI**—You can view logs using the `magento-cloud log` command.
 
 ### Log command
@@ -45,7 +45,6 @@ Enter a number to choose a log:
   [6] post-deploy
  >
 ```
-{:.no-copy}
 
 By default, the command displays the log from the Integration environment. For the Pro Staging logs, you need to specify the log location using the project ID.
 
@@ -73,23 +72,22 @@ Re-deploying environment project-integration-ID
     [2019-01-03 19:44:32] INFO: Warming up failed: http://integration-id-project.us.magentosite.cloud/
     [2019-01-03 19:44:32] NOTICE: Post-deploy is complete.
 ```
-{: .no-copy}
 
 The following logs have a common location for all Cloud projects:
 
 -  **Build log**: `var/log/cloud.log`
 -  **Debug log**: `var/log/debug.log`
 -  **Exception log**: `var/log/exception.log`
--  **Support report log**: `var/log/support_report.log`
+-  **Reports**: `var/reports/`
 
-Logs from the deploy hook are unique for each environment. The deploy log is in the following directories:
+Though the `cloud.log` file contains feedback from each stage of the deployment process, logs from the deploy hook are unique to each environment. The environment-specific deploy log is in the following directories:
 
--  **Starter and Pro Integration**: `var/log/deploy.log`
--  **Pro Staging**: `var/log/platform/<project_id>_stg/deploy.log`
--  **Pro Production**: `var/log/platform/<project_id>/deploy.log`
+-  **Starter and Pro Integration**: `/var/log/deploy.log`
+-  **Pro Staging**: `/var/log/platform/<project_id>_stg/deploy.log`
+-  **Pro Production**: `/var/log/platform/<project_id>/deploy.log`
 
 The value of `<project_id>` depends on the project ID and whether the environment is Staging or Production. For example, with a project ID of `yw1unoukjcawe`, the Staging environment user is `yw1unoukjcawe_stg` and the Production environment user is `yw1unoukjcawe`.
-Using that example, the deploy log is: `var/log/platform/yw1unoukjcawe_stg/deploy.log`
+Using that example, the deploy log is: `/var/log/platform/yw1unoukjcawe_stg/deploy.log`
 
 The log for each deployment concatenates to the specific `deploy.log` file. The following example prints the deploy log in the terminal:
 
@@ -119,28 +117,31 @@ magento-cloud log platform/<project_id>_stg/deploy
 
 ## Application logs
 
-Similar to deploy logs, application logs are unique for each environment. The following table lists application log locations on each environment:
+Similar to deploy logs, application logs are unique for each environment. For Pro Staging and Production environments, the Deploy, Post-deploy, and Cron logs are available only on the first node in the cluster.
+
+The following table lists application log locations on each environment:
 
 Log file            | Starter and Pro Integration | Pro Staging                                       | Pro Production
 ------------------- | --------------------------- | ------------------------------------------------- | -------------------------------------------
-**Deploy log**      | `var/log/deploy.log`       | `var/log/platform/<project_id>_stg/deploy.log`   | `/var/log/platform/<project_id>/deploy.log`
-**Cron log**        | `var/log/cron.log`         | `var/log/platform/<project_id>_stg/cron.log`     | `var/log/platform/<project_id>/cron.log`
-**Nginx access log**| `var/log/access.log`       | `var/log/platform/<project_id>_stg/access.log`   | `/var/log/platform/<project_id>/access.log`
-**Nginx error log** | `var/log/error.log`        | `var/log/platform/<project_id>_stg/error.log`    | `/var/log/platform/<project_id>/error.log`
-**PHP access log**  | `var/log/php.access.log`   | `var/log/platform/<project_id>_stg/php.access.log` | `/var/log/platform/<project_id>/php.access.log`
-**PHP FPM log**     | `var/log/app.log`          | `var/log/platform/<project_id>_stg/php5-fpm.log` | `var/log/platform/<project_id>/php5-fpm.log`
+**Deploy log**      | `/var/log/deploy.log`       | First node only:<br>`/var/log/platform/<project_id>_stg/deploy.log`   | First node only:<br>`/var/log/platform/<project_id>/deploy.log`
+**Post-deploy log**      | `/var/log/post_deploy.log`       | First node only:<br>`/var/log/platform/<project_id>_stg/post_deploy.log`   | First node only:<br>`/var/log/platform/<project_id>/post_deploy.log`
+**Cron log**        | `/var/log/cron.log`         | First node only:<br>`/var/log/platform/<project_id>_stg/cron.log`     | First node only:<br>`/var/log/platform/<project_id>/cron.log`
+**Nginx access log**| `/var/log/access.log`       | `/var/log/platform/<project_id>_stg/access.log`   | `/var/log/platform/<project_id>/access.log`
+**Nginx error log** | `/var/log/error.log`        | `/var/log/platform/<project_id>_stg/error.log`    | `/var/log/platform/<project_id>/error.log`
+**PHP access log**  | `/var/log/php.access.log`   | `/var/log/platform/<project_id>_stg/php.access.log` | `/var/log/platform/<project_id>/php.access.log`
+**PHP FPM log**     | `/var/log/app.log`          | `/var/log/platform/<project_id>_stg/php5-fpm.log` | `/var/log/platform/<project_id>/php5-fpm.log`
 
 ## Service logs
 
 Because each service runs in a separate container, the service logs are not available in the Integration environment. {{site.data.var.ece}} provides access to the web server container in the Integration environment only. The following service log locations are for the Pro Staging and Production environments:
 
--  **Redis log**: `var/log/platform/<project_id>_stg/redis-server-<project_id>_stg.log`
--  **Elasticseach log**: `var/log/elasticsearch/elasticsearch.log`
--  **Mail log**: `var/log/mail.log`
--  **MySQL error log**: `var/log/mysql/mysql-error.log`
--  **MySQL slow log**: `var/log/mysql/mysql-slow.log`
--  **RabbitMQ log**: `var/log/rabbitmq/[email protected]`
+-  **Redis log**: `/var/log/platform/<project_id>_stg/redis-server-<project_id>_stg.log`
+-  **Elasticseach log**: `/var/log/elasticsearch/elasticsearch.log`
+-  **Mail log**: `/var/log/mail.log`
+-  **MySQL error log**: `/var/log/mysql/mysql-error.log`
+-  **MySQL slow log**: `/var/log/mysql/mysql-slow.log`
+-  **RabbitMQ log**: `/var/log/rabbitmq/[email protected]`
 
 [hook]: {{page.baseurl}}/cloud/project/project-conf-files_magento-app.html#hooks
 [configlog]: {{page.baseurl}}/config-guide/cli/logging.html
-[slacklog]: {{page.baseurl}}/cloud/env/setup-notifications.html
+[slacklog]: {{page.baseurl}}/cloud/env/setup-notifications.html

common/images/graphql/paypal-express-checkout.svg

@@ -95,9 +95,7 @@ To resolve the issue with credentials:
 
    A snippet of messages for a successful deployment follows:
 
-   {% collapsible Click to show/hide snippet %}
-
-   ```xml
+   ```terminal
    Building application 'mymagento' (runtime type: php:7.0, tree: e8450f9)
       Generating runtime configuration.
 
@@ -163,8 +161,6 @@ To resolve the issue with credentials:
       34afd91..98c2166  master -> master
    ```
 
-   {% endcollapsible %}
-
 #### Verify the deployment
 
 To verify the deployment was successful, enter one of the URLs displayed under `Environment routes:` in a web browser.

common/images/graphql/paypal-hosted-pro.svg

@@ -21,7 +21,7 @@ The section source class is responsible for retrieving data for the section. As
 
 The public method `getSectionData` must return an array with data for private block.
 
-[Example]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Catalog/CustomerData/CompareProducts.php#L36-L45){:target="_blank"}
+[Example]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Catalog/CustomerData/CompareProducts.php#L45-L54){:target="_blank"}
 
 Add the following to your component's [dependency injection](https://glossary.magento.com/dependency-injection) configuration (`di.xml`):
 
@@ -52,7 +52,7 @@ Initialize the component as follows:
 </script>
 ```
 
-[Example]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Catalog/view/frontend/templates/product/compare/sidebar.phtml#L46-L48){:target="_blank"}
+[Example]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Catalog/view/frontend/templates/product/compare/sidebar.phtml#L50-L52){:target="_blank"}
 
 ## Configure a UI component {#config-cache-priv-how-ui}
 
@@ -62,7 +62,7 @@ The UI component renders block data on the Magento [storefront](https://glossary
 
 All properties are available in the template.
 
-[Example of defining a UI component in a layout]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Catalog/view/frontend/layout/default.xml#L11-L22){:target="_blank"}
+[Example of defining a UI component in a layout]({{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Catalog/view/frontend/layout/default.xml#L11-L32){:target="_blank"}
 
 ## Invalidate private content
 

common/images/graphql/paypal-payflow-link.svg

@@ -28,7 +28,7 @@ The ObjectManager public interface methods are:
 <p><b>Syntax:</b></p>
 <pre>
 public function getObject($className,
-     array $arguments = array());
+     array $arguments = []);
 </pre>
 <p><b>Example:</b></p>
 <pre>
@@ -61,7 +61,7 @@ $objectManagerHelper = new \Magento\TestFramework\Helper\ObjectManager($this);
 $option = $this->getMock(
     'Magento\Bundle\Model\Option',
     array('getSelections', '__wakeup', 'getData'),
-    array(),
+    [],
     '',
     false
 );
@@ -76,7 +76,7 @@ $optionCollection =
 <p><b>Syntax:</b></p>
 <pre>
 public function getConstructArguments($className,
-     array $arguments = array());
+     array $arguments = []);
 </pre>
 <p>In the Magento system, several tests introduced mocks for abstract models and blocks.</p>
 <p><b>Example:</b></p>