You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/cloud/project/services.md
+21-21Lines changed: 21 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ redirect_from:
10
10
11
11
The `services.yaml` file defines the services supported and used by {{site.data.var.ece}}, such as MySQL, Redis, and ElasticSearch. You do not need to subscribe to external service providers. This file is in the `.magento` directory of your project.
12
12
13
-
The deploy script uses the configuration files in the `.magento` directory to provision the environment with the configured services. A service becomes available to your application if it is included in the [`relationships`]({{ site.baseurl }}/cloud/project/magento-app-properties.html#relationships) property of the `.magento.app.yaml` file. The `services.yaml` file contains the _type_ and _disk_ values. Service type defines the service _name_ and _version_. Changing a service configuration causes a deployment to provision the environment with the updated services.
13
+
The deploy script uses the configuration files in the `.magento` directory to provision the environment with the configured services. A service becomes available to your application if it is included in the [`relationships`]({{ site.baseurl }}/cloud/project/magento-app-properties.html#relationships) property of the `.magento.app.yaml` file. The `services.yaml` file contains the _type_ and _disk_ values. Service type defines the service _name_ and _version_.
14
14
15
-
This affects the following environments:
15
+
Changing a service configuration causes a deployment to provision the environment with the updated services, which affects the following environments:
16
16
17
17
- All Starter environments including Production `master`
18
18
- Pro Integration environments
@@ -21,7 +21,7 @@ This affects the following environments:
21
21
22
22
## Default and supported services
23
23
24
-
We support and deploy the following services:
24
+
The cloud infrastructure supports and deploys the following services:
You can name multiple instances of each service type. For example, we could use multiple Redis instances—one for session and one for cache.
70
+
You can name multiple instances of each service type. For example, you could use multiple Redis instances—one for session and one for cache.
71
71
72
72
```yaml
73
73
redis:
@@ -79,8 +79,8 @@ redis2:
79
79
80
80
Renaming a service in the `services.yaml` file **permanently removes** the following:
81
81
82
-
- The existing service before creating a new service with the new name you specify.
83
-
- All existing data for the service is removed. We strongly recommend you [snapshot your environment]({{ site.baseurl }}/cloud/project/project-webint-snap.html) before you change the name of an existing service.
82
+
- The existing service before creating a service with the new name you specify.
83
+
- All existing data for the service is removed. Adobe strongly recommends that you [snapshot your environment]({{ site.baseurl }}/cloud/project/project-webint-snap.html) before you change the name of an existing service.
84
84
85
85
### `type`
86
86
@@ -165,19 +165,19 @@ To verify relationships in remote environments:
The following table lists the services used in {{site.data.var.ece}} and their version compatibility with the [Magento Cloud template](https://github.com/magento/magento-cloud).
168
+
The following table lists the services used in {{site.data.var.ece}} and the service version compatibility with the [Magento Cloud template](https://github.com/magento/magento-cloud). The {{site.data.var.ee}} columns show the service versions that are compatible with that latest version for {{site.data.var.ee}}. The **Version Notes** column specifically calls out compatibility differences from latest, and any other relevant service compatibility notes.
| `elasticsearch` | 7.7, 7.9 | **{{site.data.var.ee}} version 2.3.5 and later**— 5.2, 6.5, 6.8, 7.5, 7.7, 7.9<br>**{{site.data.var.ee}} version 2.3.1 to 2.3.4**— 5.2, 6.5<br>**{{site.data.var.ee}} version 2.3.0**— 5.2 | **{{site.data.var.ee}} version 2.2.8 and later**— 5.2, 6.5 <br>**{{site.data.var.ee}} version 2.2.0 to 2.2.7**— 5.2 |
174
-
| `mariadb` | 10.2, 10.3, 10.4 | **{{site.data.var.ee}} version 2.3.0 to 2.3.5**–10.1 to 10.2<br>| 10.1 to 10.2 |
175
-
| `nginx` | | 1.9 | 1.9 |
176
-
| `node` | | 6, 8, 10, 11 | 6, 8, 10, 11 |
177
-
| `php` | 7.3, 7.4 | **{{site.data.var.ee}} version 2.3.4 and later**— 7.1, 7.2, 7.3<br>**{{site.data.var.ee}} version 2.3.3**— 7.1, 7.2, 7.3<br>**{{site.data.var.ee}} version 2.3.0 to 2.3.2**— 7.1, 7.2 | **{{site.data.var.ee}} version 2.2.10 and later**— 7.1, 7.2<br>**{{site.data.var.ee}} version 2.2.5 to 2.2.9**— 7.0, 7.1<br>**{{site.data.var.ee}} version 2.2.4 and earlier**— 7.0.2, 7.0.4, ~7.0.6, 7.1<br><br>**Note:** Beginning with {{ site.data.var.ct }} v2002.1.0, you must use PHP version 7.1.3 or later for both 2.2 and 2.3. |
178
-
| `rabbitmq` | 3.8 | **{{site.data.var.ee}} version 2.3.5**–3.8<br>**{{site.data.var.ee}} version 2.3.3 - 2.3.4**— 3.7, 3.8<br>**{{site.data.var.ee}} version 2.3.0 to 2.3.3**— 3.7| 3.5 |
179
-
| `redis` | 5.x, 6.x | **{{site.data.var.ee}} version 2.3.1 - 2.3.7**–5.x, 6.x<br>**{{site.data.var.ee}} version 2.3.0**— 3.2| 3.2, 5.0, 6.x |
180
-
| `varnish` | 6.x | **{{site.data.var.ee}} version 2.3.3 to 2.3.5**— 4.0, 5.0, 6.2<br>**{{site.data.var.ee}} version 2.3.0 to 2.3.2**— 4.0, 5.0 | 4.0, 5.0<br>**Note:** On Cloud projects, you must use the [Fastly service]({{site.baseurl}}/cloud/cdn/cloud-fastly.html) for caching. Varnish is available only for local development. |
171
+
| Service | {{site.data.var.ee}} 2.4 | {{site.data.var.ee}} 2.3 | {{site.data.var.ee}} 2.2 | Version Notes |
| `php` | 7.3, 7.4 | 7.2, 7.3, 7.4 | 7.1, 7.2 | **Note:** Beginning with {{ site.data.var.ct }} v2002.1.0, you must use PHP template version 7.1.3 or later for both 2.2 and 2.3.<br><br>**Commerce 2.3.3**— 7.1, 7.2, 7.3<br>**Commerce 2.3.0 to 2.3.2**— 7.1, 7.2<br>**Commerce 2.2.5 to 2.2.9**— 7.0, 7.1<br>**Commerce 2.2.4 and earlier**— 7.0.2, 7.0.4, ~7.0.6, 7.1 |
| `varnish` | 6.x | 4.0, 5.0, 6.2| 4.0, 5.0| **Note:** On Cloud projects, you must use the [Fastly service]({{site.baseurl}}/cloud/cdn/cloud-fastly.html) for caching. Varnish is available only for local development.<br><br>**Commerce 2.3.0 to 2.3.2**— 4.0, 5.0 |
181
181
182
182
{:.bs-callout-info}
183
183
When you set up the Elasticsearch service, check to ensure that you use a version that is compatible with the installed [Elasticsearch PHP](https://github.com/elastic/elasticsearch-php) client. See [Check Elasticsearch software compatibility]({{ site.baseurl }}/cloud/project/services-elastic.html#elasticsearch-software-compatibility).
@@ -195,9 +195,9 @@ To maintain store security, update installed software versions before they reach
195
195
196
196
You can upgrade the installed service version for compatibility with the {{site.data.var.ee}} version deployed in your Cloud environment.
197
197
198
-
You cannot downgrade the service version for an installed service directly. However, you can create a new service with the required version. See [Downgrade service version](#downgrade-version).
198
+
You cannot downgrade the service version for an installed service directly. However, you can create a service with the required version. See [Downgrade service version](#downgrade-version).
199
199
200
-
Use the [Service versions](#service-versions) table to check service version compatibility by {{site.data.var.ee}} version. Note that some service versions supported by {{ site.data.var.ee }} are not supported on {{ site.data.var.ece }}.
200
+
Use the [Service versions](#service-versions) table to check service version compatibility by {{site.data.var.ee}} version. Some service versions supported by {{ site.data.var.ee }} are not supported on {{ site.data.var.ece }}.
201
201
202
202
### Upgrade installed service version
203
203
@@ -241,7 +241,7 @@ You cannot downgrade an installed service directly. You have two options:
241
241
242
242
- Rename an existing service with the new version, which removes the existing service and data, and adds a new one.
243
243
244
-
- Create a new service and save the data from the existing service.
244
+
- Create a service and save the data from the existing service.
245
245
246
246
When you change the service version, you must update the service configuration in the `services.yaml` file, and update the relationships in the `.magento.app.yaml` file.
247
247
@@ -251,7 +251,7 @@ To downgrade a service version by renaming an existing service:
251
251
1. Rename the existing service in the `.magento/services.yaml` file and change the version.
252
252
253
253
{:.bs-callout-warning}
254
-
Renaming an existing service replaces it and deletes all data. If you need to retain the data, create a new service instead of renaming the existing one.
254
+
Renaming an existing service replaces it and deletes all data. If you need to retain the data, create a service instead of renaming the existing one.
255
255
256
256
For example, to downgrade the MariaDB version for the _mysql_ service from version 10.3 to 10.2, change the existing _service-id_ and _type_ configuration.
0 commit comments