Skip to content

Commit 43fb367

Browse files
author
gitName
committed
edits
1 parent 9982f9f commit 43fb367

File tree

2 files changed

+18
-29
lines changed

2 files changed

+18
-29
lines changed

articles/api-center/includes/delete-api-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ You can delete an integration using the portal or the Azure CLI.
2323
#### [Portal](#tab/portal)
2424

2525
1. In the [portal](https://portal.azure.com), navigate to your API center.
26-
1. Under **Assets**, select **Environments** > **Integration (preview)**.
27-
1. Select the integration, and then select **Delete** (trash can icon).
26+
1. Under **Assets**, select **Environments** > **Links (preview)**.
27+
1. Select the link, and then select **Delete** (trash can icon).
2828

2929
#### [Azure CLI](#tab/cli)
3030

articles/api-center/synchronize-aws-gateway-apis.md

Lines changed: 16 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -89,31 +89,8 @@ Take note of the **Secret identifier** of each secret, a URI similar to `https:/
8989

9090
## Integrate an Amazon API Gateway
9191

92-
You can integrate an Amazon API Gateway to your API center using the Azure CLI.
93-
94-
<!--
95-
#### [Portal](#tab/portal)
96-
97-
1. In the [portal](https://portal.azure.com), navigate to your API center.
98-
1. Under **Assets**, select **Environments**.
99-
1. Select **Integrations (preview)** > **+ New integration** > **From Amazon API Gateway**.
100-
1. In the **Integrate your Amazon API Gateway service** page:
101-
1. Under **Configure AWS credentials using Azure Key Vault**, enter or select the Key Vault secret identifiers for the **AWS access key** and **AWS secret access key** you stored previously. Also, select the **AWS region** where the Amazon API Gateway is deployed.
102-
1. In **Integration details**, enter an identifier.
103-
1. In **Environment details**, enter an **Environment title** (name), **Environment type**, and optional **Description**.
104-
1. In **API Details**:
105-
1. Select a **Lifecycle** for the synchronized APIs. (You can update this value for the APIs after they're added to your API center.)
106-
1. Optionally, select whether to include API definitions.
107-
1. Select **Create**.
108-
109-
Add image of integrating AWS g/w in portal
110-
111-
112-
#### [Azure CLI](#tab/cli)
113-
114-
--->
115-
116-
Run the `az apic integration create aws` command to integrate an Amazon API Gateway to your API center.
92+
93+
Run the [az apic integration create aws](/cli/azure/apic/integration/create#az-apic-integration-create-aws) (preview) command command to integrate an Amazon API Gateway to your API center.
11794

11895
* Provide the names of the resource group, API center, and integration.
11996

@@ -128,12 +105,24 @@ az apic integration create aws \
128105
--aws-secret-access-key-reference <secret-access-key-uri>
129106
--aws-region-name <aws-region>
130107
```
131-
108+
---
132109

133110
The environment is added in your API center. The Amazon API Gateway APIs are imported to the API center inventory.
134111

112+
## Delete an integration
113+
114+
While an API source is integrated, you can't delete synchronized APIs from your API center. If you need to, you can delete the integration. When you delete an integration:
115+
116+
* The synchronized APIs in your API center inventory are deleted
117+
* The environment and deployments associated with the API source are deleted
135118

136-
[!INCLUDE [delete-api-integration](includes/delete-api-integration.md)]
119+
To delete an integration using the Azure CLI, run the [az apic integration delete](/cli/azure/apic/integration#az-apic-integration-delete) (preview) command. Provide the names of the resource group, API center, and integration.
120+
121+
```azurecli
122+
az apic integration delete \
123+
--resource-group <resource-group-name> \
124+
--service-name <api-center-name> \
125+
--integration-name <integration-name> \
137126
138127
## Related content
139128

0 commit comments

Comments
 (0)