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
Copy file name to clipboardExpand all lines: pr-preview/pr-700/deploying/integration-requests/index.html
+37-27Lines changed: 37 additions & 27 deletions
Original file line number
Diff line number
Diff line change
@@ -996,7 +996,7 @@
996
996
997
997
<h1>Integration Requests</h1>
998
998
999
-
<p>Integration requests streamline your deployment process by automatically associating the necessary OAuth integrations with your content, eliminating the need for manual configuration and ensuring that your deployed content has immediate access to the external services that it depends on.</p>
999
+
<p>Integration requests streamline your deployment process by automatically associating the necessary OAuth integrations with your content, eliminating the need for manual configuration and ensuring that your deployed content has immediate access to the external resources that it depends on.</p>
1000
1000
<p>You can define integration requests for your content by defining <code>integration_requests</code> in your content's <code>manifest.json</code> file. The base <code>manifest.json</code> file can be produced using the <ahref="../../commands/write-manifest/"><code>write-manifest</code></a> command, but you will need to edit the file by hand to add the <code>integration_requests</code>.</p>
<p>During deployment, these integration requests will be processed, and the specified integration specifications will be matched to integrations that are available on the Connect server. If a matching integration is found, it will be used for the deployment. If no matching integration is found, the deployment will fail with an error message indicating that the integration request could not be satisfied.</p>
@@ -1049,30 +1049,34 @@ <h3 id="integration-request-specification">Integration Request Specification<a c
1049
1049
</tr>
1050
1050
</tbody>
1051
1051
</table>
1052
-
<p>Possible values for <code>type</code> include:
1053
-
- <code>azure</code>
1054
-
- <code>azure-openai</code>
1055
-
- <code>sharepoint</code>
1056
-
- <code>msgraph</code>
1057
-
- <code>bigquery</code>
1058
-
- <code>drive</code>
1059
-
- <code>sheets</code>
1060
-
- <code>vertex-ai</code>
1061
-
- <code>databricks</code>
1062
-
- <code>github</code>
1063
-
- <code>salesforce</code>
1064
-
- <code>snowflake</code>
1065
-
- <code>connect</code>
1066
-
- <code>aws</code>
1067
-
- <code>custom</code></p>
1068
-
<p>Possible values for <code>auth_type</code> include:
1069
-
- <code>Viewer</code>
1070
-
- <code>Service Account</code>
1071
-
- <code>Visitor API Key</code></p>
1052
+
<p>Possible values for <code>type</code> include:</p>
1053
+
<ul>
1054
+
<li><code>azure</code></li>
1055
+
<li><code>azure-openai</code></li>
1056
+
<li><code>sharepoint</code></li>
1057
+
<li><code>msgraph</code></li>
1058
+
<li><code>bigquery</code></li>
1059
+
<li><code>drive</code></li>
1060
+
<li><code>sheets</code></li>
1061
+
<li><code>vertex-ai</code></li>
1062
+
<li><code>databricks</code></li>
1063
+
<li><code>github</code></li>
1064
+
<li><code>salesforce</code></li>
1065
+
<li><code>snowflake</code></li>
1066
+
<li><code>connect</code></li>
1067
+
<li><code>aws</code></li>
1068
+
<li><code>custom</code></li>
1069
+
</ul>
1070
+
<p>Possible values for <code>auth_type</code> include:</p>
1071
+
<ul>
1072
+
<li><code>Viewer</code></li>
1073
+
<li><code>Service Account</code></li>
1074
+
<li><code>Visitor API Key</code></li>
1075
+
</ul>
1072
1076
<p>An integration request can contain any combination of the fields listed above, and the correct combination will vary by situation.</p>
<h4id="using-the-integration-guid">Using the integration guid<aclass="headerlink" href="#using-the-integration-guid" title="Permanent link">#</a></h4>
1075
-
<p>If the content will only ever be deployed to a single server, the easiest way to make sure an OAuth integration gets automatically associated with it is by only listing the OAuth integration <code>guid</code> in the integration request:</p>
1079
+
<p>If the content will only ever be deployed to a single server, the easiest way to make sure the correct OAuth integration gets automatically associated is by listing the OAuth integration <code>guid</code> in the integration request:</p>
@@ -1092,11 +1096,17 @@ <h4 id="using-the-integration-name-and-template">Using the integration name and
1092
1096
</code></pre></div>
1093
1097
<h4id="using-the-name-template-and-config">Using the name, template, and config<aclass="headerlink" href="#using-the-name-template-and-config" title="Permanent link">#</a></h4>
0 commit comments