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.
* Added Configuration Hierarchy for application settings for Magento Commerce on Clout
* Update src/cloud/live/sens-data-over.md
* Added table and populated with full descriptions
* Added missing info to table
* Editorial & link updates for config hierarchy tbl
* Corrected table order & text
* Updated punctuation
Co-authored-by: Barny Shergold <[email protected]>
Co-authored-by: Margaret Eker <[email protected]>
Co-authored-by: hguthrie <[email protected]>
Copy file name to clipboardExpand all lines: src/cloud/live/sens-data-over.md
+18-3Lines changed: 18 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ You must have [environment-level, Admin role privileges][admin] to complete conf
13
13
14
14
## Consistent configuration
15
15
16
-
The database contains default configurations for your Magento store. When you update configurations in the {{site.data.var.ece}} environments using the Magento Admin panel, your configuration changes apply to the `app/etc/config.php` file. You can then use this file to manage and synchronize the Magento application configuration for your local environment and across each Cloud environment.
16
+
The database contains default configurations for your Magento store. When you update configurations in the {{site.data.var.ece}} environments using the Magento Admin panel or the Magento CLI `bin/magento config:set` command, your configuration changes apply to the `app/etc/config.php` file. You can then use this file to manage and synchronize the Magento application configuration for your local environment and across each Cloud environment.
17
17
18
18
Use the `{{site.data.var.ct}}` command in the remote environment to generate a `config.php` file:
19
19
@@ -43,7 +43,9 @@ Because {{site.data.var.ece}} supports only the Magento production and maintenan
43
43
44
44
### Sensitive data
45
45
46
-
Sensitive values are _not_ stored in the `app/etc/config.php` file. Any sensitive configurations export to the `app/etc/config.php` file during the `config:dump` process. We recommend using environment variables to store sensitive values. For an example, see [Add Magento authentication keys][auth].
46
+
Sensitive values are _not_ stored in the `app/etc/config.php` file. Any sensitive configurations export to the `app/etc/env.php` file when you use the `bin/magento app:config:dump` Magento CLI command. For Cloud projects, we recommend using {{ site.data.var.ece }} environment variables to store sensitive values. For an example, see [Add Magento authentication keys][auth].
47
+
48
+
You can also set sensitive values using the Magento CLI command: `bin/magento config:sensitive:set`, see [Sensitive or system-specific settings] in the _Configuration Guide_.
47
49
48
50
### SCD performance
49
51
@@ -60,6 +62,17 @@ All system configurations are set during build and deploy according to the follo
60
62
1. If an environment variable does not exist, use the configuration from a `MAGENTO_CLOUD_RELATIONSHIPS` name-value pair in the [`.magento.app.yaml` file][app-yaml]. Ignore the default configuration.
61
63
1. If an environment variable does not exist and `MAGENTO_CLOUD_RELATIONSHIPS` does not contain a name-value pair, remove all customized configuration and use the values from the default configuration.
62
64
65
+
If the same setting is configured in multiple places, Magento relies on the following configuration hierarchy to determine which value to apply to the environment :
66
+
67
+
|Priority|Configuration<br/>Method|Description|
68
+
|---|---|---|
69
+
|1 | Project Web UI<br>environment variables | Values added from the _Variables_ tab of environment configuration in the Project Web UI. We recommend specifying values here for sensitive or environment-specific configurations. Settings specified here cannot be edited from the Magento Admin. See [Environment configuration variables][].|
70
+
|2 |`.magento.app.yaml`| Values added in the `variables` section of the `.magento.app.yaml` file. We recommend specifying values here to ensure consistent configuration across all environments. **Do not specify sensitive values in the `.magento.app.yaml` file.** See [Application settings][app-yaml].|
71
+
|3 |`app/etc/env.php`| Environment-specific configuration values stored here are added by using the Magento `app:config:dump` command. Set the system-specific and sensitive values using environment variables or the Magento CLI. See [Sensitive data](#sensitive-data). The `env.php` file is **not** included in source control.|
72
+
|4 |`app/etc/config.php`| Values stored here are added by using the Magento `app:config:dump` command. Shared configuration values are added to `config.php`. Set shared configuration from the Magento Admin or using the Magento CLI. See [Consistent configuration](#consistent-configuration). The `config.php` file is included in source control.|
73
+
|5 | Database | Values stored here are added by setting configurations in the Magento Admin. Note that configurations set using any of the preceding methods are locked (greyed out) and cannot be edited from the Magento Admin.|
74
+
|6 |`config.xml`| Many configurations have default values set in a the `config.xml` file for a module. If Magento cannot find any value set by any of the preceding methods, it falls back to the default value, if set.|
75
+
63
76
## Procedure to manage your settings
64
77
65
78
The following illustrates a high-level overview of this process:
@@ -170,8 +183,10 @@ This process **overwrites** the store configuration; only do the following if th
0 commit comments