Skip to content
This repository was archived by the owner on Nov 19, 2024. It is now read-only.

Commit d3c3915

Browse files
hellotarankeharper
authored andcommitted
Update create-integration.md (#5786)
* Update create-integration.md * Update create-integration.md * Update create-integration.md * Update create-integration.md * Update create-integration.md
1 parent bc55666 commit d3c3915

File tree

2 files changed

+29
-5
lines changed

2 files changed

+29
-5
lines changed

guides/v2.2/get-started/create-integration.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ To develop a module, you must:
9292
"name": "Vendor1_Module1",
9393
"description": "create integration from config",
9494
"require": {
95-
"php": "~5.5.0|~5.6.0|~7.0.0",
95+
"php": "~7.0.13|~7.1.0|~7.2.0",
9696
"magento/framework": "2.0.0",
9797
"magento/module-integration": "2.0.0"
9898
},
@@ -170,7 +170,19 @@ To develop a module, you must:
170170

171171
`$this->integrationManager->processIntegrationConfig(['TestIntegration']);`
172172

173-
`testIntegration` must refer to your `etc/integration.xml` file, and the integration name value must be the same.
173+
`testIntegration` must refer to your `etc/integration/config.xml` file, and the integration name value must be the same.
174+
175+
The following example demonstrates a minimal 'config.xml' file.
176+
177+
```xml
178+
<integrations>
179+
<integration name="TestIntegration">
180+
<email>[email protected]</email>
181+
<endpoint_url>https://example.com</endpoint_url>
182+
<identity_link_url>https://example.com/identity_link_url</identity_link_url>
183+
</integration>
184+
</integrations>
185+
``
174186

175187
Also, be sure to change the path after `namespace` for your vendor and module names.
176188

guides/v2.3/get-started/create-integration.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ To develop a module, you must:
8686
"name": "Vendor1_Module1",
8787
"description": "create integration from config",
8888
"require": {
89-
"php": "~5.5.0|~5.6.0|~7.0.0",
89+
"php": "~7.1.3|~7.2.0|~7.3.0",
9090
"magento/framework": "2.0.0",
9191
"magento/module-integration": "2.0.0"
9292
},
@@ -164,7 +164,19 @@ To develop a module, you must:
164164

165165
`$this->integrationManager->processIntegrationConfig(['testIntegration']);`
166166

167-
`testIntegration` must refer to your `etc/integrations/config.xml` file, and the integration name value must be the same.
167+
`testIntegration` must refer to your `etc/integration/config.xml` file, and the integration name value must be the same.
168+
169+
The following example demonstrates a minimal `config.xml` file.
170+
171+
```xml
172+
<integrations>
173+
<integration name="TestIntegration">
174+
<email>[email protected]</email>
175+
<endpoint_url>https://example.com</endpoint_url>
176+
<identity_link_url>https://example.com/identity_link_url</identity_link_url>
177+
</integration>
178+
</integrations>
179+
```
168180

169181
Also, be sure to change the path after `namespace` for your vendor and module names.
170182

@@ -211,7 +223,7 @@ In the following example, the test integration requires access to the following
211223
212224
### Pre-configure the integration {#preconfig}
213225
214-
Your module can optionally provide a configuration file `config.xml` so that the integration can be automatically pre-configured with default values. To enable this feature, create the `config.xml` file in the `etc/integration` directory.
226+
Your module can optionally provide values in configuration file `config.xml`, so that the integration can be automatically pre-configured with default values. To enable this feature, update the `config.xml` file in the `etc/integration` directory.
215227
216228
{: .bs-callout-info }
217229
If you pre-configure the integration, the values cannot be edited from the [admin](https://glossary.magento.com/admin) panel.

0 commit comments

Comments
 (0)