diff --git a/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api.md b/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api.md index 53f65b22cee..ca12845f972 100644 --- a/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api.md +++ b/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api.md @@ -1,8 +1,8 @@ --- -title: Connect Azure DevOps repositories to Catalog with the {{site.konnect_short_name}} API +title: Connect Azure DevOps repositories to {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API permalink: /how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api/ content_type: how_to -description: Learn how to connect Azure DevOps repositories to your {{site.konnect_catalog}} services in {{site.konnect_short_name}} using the Konnect API. +description: Learn how to connect Azure DevOps repositories to your {{site.konnect_catalog}} Classic services in {{site.konnect_short_name}} using the Konnect API. products: - catalog works_on: @@ -17,8 +17,8 @@ search_aliases: - devops - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Azure DevOps reference @@ -49,6 +49,8 @@ prereqs: ``` --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the Azure DevOps integration Before you can discover Azure DevOps repositories in {{site.konnect_catalog}}, export your Azure DevOps organization name exactly as it appears in Azure DevOps: @@ -97,7 +99,7 @@ body: Once authorized, resources from your Azure DevOps account are discoverable in the UI. -## Create a Service in Catalog +## Create a Service in {{site.konnect_catalog}} Classic Create a service to map to your Azure DevOps resources: @@ -120,7 +122,7 @@ capture: ## List Azure DevOps resources -Before you map Azure DevOps resources to a service in Catalog, locate the resources that {{site.konnect_short_name}} ingests from Azure DevOps: +Before you map Azure DevOps resources to a service in {{site.konnect_catalog}} Classic, locate the resources that {{site.konnect_short_name}} ingests from Azure DevOps: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui.md b/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui.md index cc3f4b913c1..c61dfad879c 100644 --- a/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui.md +++ b/app/_how-tos/catalog/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui.md @@ -1,8 +1,8 @@ --- -title: Connect Azure DevOps repositories to Catalog with the {{site.konnect_short_name}} UI +title: Connect Azure DevOps repositories to {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI permalink: /how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui/ content_type: how_to -description: Learn how to connect Azure DevOps repositories to your {{site.konnect_catalog}} services in {{site.konnect_short_name}} using the UI. +description: Learn how to connect Azure DevOps repositories to your {{site.konnect_catalog}} Classic services in {{site.konnect_short_name}} using the UI. products: - catalog works_on: @@ -14,8 +14,8 @@ search_aliases: - azure repos - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Azure DevOps reference @@ -26,7 +26,7 @@ related_resources: automated_tests: false tldr: q: How do I connect an Azure DevOps repository to a service in {{site.konnect_short_name}}? - a: Configure the Azure DevOps integration with your organization name and PAT, create a {{site.konnect_catalog}} service, then map the discovered Azure DevOps repository resource to that {{site.konnect_catalog}} service. + a: Configure the Azure DevOps integration with your organization name and PAT, create a {{site.konnect_catalog}} Classic service, then map the discovered Azure DevOps repository resource to that {{site.konnect_catalog}} Classic service. prereqs: skip_product: true inline: @@ -43,9 +43,11 @@ prereqs: > Your PAT can be created with an expiration period of your choice, up to a maximum of one year. Make sure to renew the PAT before it expires to avoid interruptions. --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the Azure DevOps integration -Before you can discover Azure DevOps repositories in {{site.konnect_catalog}}, you must configure the integration: +Before you can discover Azure DevOps repositories in {{site.konnect_catalog}} Classic, you must configure the integration: 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. In the {{site.konnect_catalog}} sidebar, click **Integrations**. @@ -60,9 +62,9 @@ Before you can discover Azure DevOps repositories in {{site.konnect_catalog}}, y If you don't immediately see resources, try manually syncing your Azure DevOps integration. From the {{site.konnect_short_name}} UI, navigate to the Azure DevOps integration that you just installed. Then, from the **Actions** dropdown menu, select **Sync Now**. -## Create a {{site.konnect_catalog}} service and map the Azure DevOps resources +## Create a {{site.konnect_catalog}} Classic service and map the Azure DevOps resources -After you configure the Azure DevOps integration, create a service in {{site.konnect_catalog}} and map an Azure DevOps repository resource to it. +After you configure the Azure DevOps integration, create a service in {{site.konnect_catalog}} Classic and map an Azure DevOps repository resource to it. {:.info} > In this tutorial, we’ll refer to your Azure DevOps repository as `azure-devops-repository`. diff --git a/app/_how-tos/catalog/discover-and-govern-apis-with-service-catalog.md b/app/_how-tos/catalog/discover-and-govern-apis-with-service-catalog.md index 62e326f3f27..d3b344f44af 100644 --- a/app/_how-tos/catalog/discover-and-govern-apis-with-service-catalog.md +++ b/app/_how-tos/catalog/discover-and-govern-apis-with-service-catalog.md @@ -1,8 +1,8 @@ --- -title: Discover and govern APIs with Catalog +title: Discover and govern APIs with {{site.konnect_catalog}} Classic permalink: /how-to/discover-and-govern-apis-with-service-catalog/ content_type: how_to -description: Learn how to discover APIs in AWS API Gateway, SwaggerHub, and GitHub with {{site.konnect_catalog}} and govern them with scorecards. +description: Learn how to discover APIs in AWS API Gateway, SwaggerHub, and GitHub with {{site.konnect_catalog}} Classic and govern them with scorecards. products: - catalog works_on: @@ -15,8 +15,8 @@ entities: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: AWS API Gateway reference @@ -27,12 +27,12 @@ automated_tests: false tldr: q: How do I discover and govern third-party APIs in {{site.konnect_short_name}}? a: | - {{site.konnect_catalog}} allows you to find and centrally view all APIs from these integrations and map them to a {{site.konnect_catalog}} service. First, authorize the integrations in {{site.konnect_catalog}} for AWS API Gateway, GitHub, and SwaggerHub. Then, create a {{site.konnect_catalog}} service and map resources from the integrations to the service. Finally, add a service documentation scorecard to your service to govern API documentation standards. + {{site.konnect_catalog}} Classic allows you to find and centrally view all APIs from these integrations and map them to a {{site.konnect_catalog}} Classic service. First, authorize the integrations in {{site.konnect_catalog}} Classic for AWS API Gateway, GitHub, and SwaggerHub. Then, create a {{site.konnect_catalog}} Classic service and map resources from the integrations to the service. Finally, add a service documentation scorecard to your service to govern API documentation standards. prereqs: inline: - title: "{{site.konnect_short_name}} roles" content: | - To configure {{site.konnect_catalog}} integrations, services, and scorecards, you need the following [roles in {{site.konnect_short_name}}](/konnect-platform/teams-and-roles/#service-catalog): + To configure {{site.konnect_catalog}} Classic integrations, services, and scorecards, you need the following [roles in {{site.konnect_short_name}}](/konnect-platform/teams-and-roles/#service-catalog): * Integration Admin * Scorecard Admin * Service Admin @@ -47,7 +47,7 @@ prereqs: icon_url: /assets/icons/third-party/swaggerhub.svg - title: GitHub content: | - To integrate GitHub with {{site.konnect_catalog}}, you need the following: + To integrate GitHub with {{site.konnect_catalog}} Classic, you need the following: * Sufficient permissions in GitHub to authorize third-party applications and install the {{site.konnect_short_name}} GitHub App * A GitHub organization * A repository that you want to pull in to {{site.konnect_short_name}}. You can grant access to either all repositories or selected repositories during the authorization process. You can name your GitHub repository whatever you'd like. In this tutorial, we'll refer to your GitHub repository as `github-repo`. @@ -58,11 +58,13 @@ tools: - deck --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the AWS API Gateway, GitHub, and SwaggerHub integrations -In this tutorial, we'll be discovering APIs and API specs from AWS API Gateway, GitHub, and SwaggerHub in {{site.konnect_catalog}}. {{site.konnect_catalog}} allows you to find and centrally view all APIs from these integrations and map them to a {{site.konnect_catalog}} service. +In this tutorial, we'll be discovering APIs and API specs from AWS API Gateway, GitHub, and SwaggerHub in {{site.konnect_catalog}} Classic. {{site.konnect_catalog}} Classic allows you to find and centrally view all APIs from these integrations and map them to a {{site.konnect_catalog}} Classic service. -Before you can discover APIs in {{site.konnect_catalog}}, you must configure the third-party integrations. +Before you can discover APIs in {{site.konnect_catalog}} Classic, you must configure the third-party integrations. ### Configure the AWS API Gateway integration @@ -91,9 +93,9 @@ The {{site.konnect_short_name}} application can be managed from GitHub as a [Git 1. In the **Instance name** field, enter `swaggerhub-test`. 1. Click **Save**. -## Create a {{site.konnect_catalog}} service and map the API resources +## Create a {{site.konnect_catalog}} Classic service and map the API resources -Now that your integrations are configured, you can create a {{site.konnect_catalog}} service to map the ingested APIs. +Now that your integrations are configured, you can create a {{site.konnect_catalog}} Classic service to map the ingested APIs. {:.info} > In this tutorial, we'll refer to your ingested resources like the following: @@ -113,11 +115,11 @@ Now that your integrations are configured, you can create a {{site.konnect_catal 1. Select `github-repo`. 1. Click **Map 3 Resources**. -Your integration APIs are now discoverable from one {{site.konnect_catalog}} service. +Your integration APIs are now discoverable from one {{site.konnect_catalog}} Classic service. ## Govern the APIs with scorecards -Now that you've discovered and mapped the APIs to a {{site.konnect_catalog}} service, you can govern the service documentation of these ingested APIs with a [scorecard](/catalog/scorecards/). The built-in service documentation scorecard will alert you when your APIs don't adhere to [API documentation best practices](/catalog/scorecards/#service-documentation-linting). +Now that you've discovered and mapped the APIs to a {{site.konnect_catalog}} Classic service, you can govern the service documentation of these ingested APIs with a [scorecard](/catalog/scorecards/). The built-in service documentation scorecard will alert you when your APIs don't adhere to [API documentation best practices](/catalog/scorecards/#service-documentation-linting). 1. In the {{site.konnect_short_name}} sidebar, click [**Catalog**](https://cloud.konghq.com/service-catalog/). 1. In the Catalog sidebar, click **Scorecards**. diff --git a/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-api.md b/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-api.md index 3500ec21ee0..2480299e8e4 100644 --- a/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-api.md +++ b/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-api.md @@ -1,8 +1,8 @@ --- -title: Discover AWS Gateway APIs in Catalog with the Konnect API +title: Discover AWS Gateway APIs in {{site.konnect_catalog}} Classic with the Konnect API permalink: /how-to/discover-aws-gateway-apis-using-konnect-api/ content_type: how_to -description: Learn how to connect an AWS Gateway API to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the API. +description: Learn how to connect an AWS Gateway API to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the API. products: - catalog works_on: @@ -15,20 +15,20 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: AWS API Gateway reference url: /catalog/integrations/aws-api-gateway/ - - text: "Discover AWS Gateway APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI" + - text: "Discover AWS Gateway APIs in {{site.konnect_catalog}} Classic with the Konnect UI" url: /how-to/discover-aws-gateway-apis-using-konnect-ui/ - text: Discover and govern APIs with {{site.konnect_catalog}} url: /how-to/discover-and-govern-apis-with-service-catalog/ automated_tests: false tldr: q: How do I discover AWS API Gateway API in {{site.konnect_short_name}}? - a: Install the AWS API Gateway integration in {{site.konnect_short_name}} and authorize access with your {{site.konnect_catalog}} role ARN, then link an API to your {{site.konnect_catalog}} service. + a: Install the AWS API Gateway integration in {{site.konnect_short_name}} and authorize access with your {{site.konnect_catalog}} Classic role ARN, then link an API to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -39,13 +39,15 @@ prereqs: icon_url: /assets/icons/aws.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the AWS API Gateway integration -Before you can discover APIs in {{site.konnect_catalog}}, you must configure the AWS API Gateway integration. +Before you can discover APIs in {{site.konnect_catalog}} Classic, you must configure the AWS API Gateway integration. {% include /catalog/aws-api-gateway-integration.md %} -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your AWS API Gateway resources: @@ -69,7 +71,7 @@ export AWS_SERVICE_ID='YOUR-SERVICE-ID' ## List AWS API Gateway resources -Before you can map your AWS API Gateway resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from AWS API Gateway: +Before you can map your AWS API Gateway resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from AWS API Gateway: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-ui.md b/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-ui.md index c9681a9836e..d02f2eb6f3d 100644 --- a/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-ui.md +++ b/app/_how-tos/catalog/discover-aws-gateway-apis-using-konnect-ui.md @@ -1,8 +1,8 @@ --- -title: Discover AWS Gateway APIs in Catalog with the Konnect UI +title: Discover AWS Gateway APIs in {{site.konnect_catalog}} Classic with the Konnect UI permalink: /how-to/discover-aws-gateway-apis-using-konnect-ui/ content_type: how_to -description: Learn how to connect an AWS Gateway API to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the UI. +description: Learn how to connect an AWS Gateway API to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the UI. products: - catalog works_on: @@ -15,20 +15,20 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: AWS API Gateway reference url: /catalog/integrations/aws-api-gateway/ - - text: "Discover AWS Gateway APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" + - text: "Discover AWS Gateway APIs in {{site.konnect_catalog}} Classic with the Konnect API" url: /how-to/discover-aws-gateway-apis-using-konnect-api/ - text: Discover and govern APIs with {{site.konnect_catalog}} url: /how-to/discover-and-govern-apis-with-service-catalog/ automated_tests: false tldr: q: How do I discover AWS API Gateway API in {{site.konnect_short_name}}? - a: Install the AWS API Gateway integration in {{site.konnect_short_name}} and authorize access with your {{site.konnect_catalog}} role ARN, then link an API to your {{site.konnect_catalog}} service. + a: Install the AWS API Gateway integration in {{site.konnect_short_name}} and authorize access with your {{site.konnect_catalog}} Classic role ARN, then link an API to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -39,15 +39,17 @@ prereqs: icon_url: /assets/icons/aws.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the AWS API Gateway integration -Before you can discover APIs in {{site.konnect_catalog}}, you must configure the AWS API Gateway integration. +Before you can discover APIs in {{site.konnect_catalog}} Classic, you must configure the AWS API Gateway integration. {% include /catalog/aws-api-gateway-integration.md %} -## Create a {{site.konnect_catalog}} service and map the API resources +## Create a {{site.konnect_catalog}} Classic service and map the API resources -Now that your integration is configured, you can create a {{site.konnect_catalog}} service to map the ingested APIs. +Now that your integration is configured, you can create a {{site.konnect_catalog}} Classic service to map the ingested APIs. {:.info} > In this tutorial, we'll refer to your ingested AWS API Gateway API as `aws-api`. @@ -62,7 +64,7 @@ Now that your integration is configured, you can create a {{site.konnect_catalog 1. Select `aws-api`. 1. Click **Map 1 Resource**. -Your integration APIs are now discoverable from one {{site.konnect_catalog}} service. +Your integration APIs are now discoverable from one {{site.konnect_catalog}} Classic service. {:.info} > You might need to manually sync your AWS API Gateway integration for resources to appear. In the {{site.konnect_short_name}} UI, by navigate to the AWS API Gateway integration you just installed and select **Sync Now** from the **Actions** dropdown menu. diff --git a/app/_how-tos/catalog/discover-azure-apis-with-konnect-api.md b/app/_how-tos/catalog/discover-azure-apis-with-konnect-api.md index cd245bb9571..40e40e50d96 100644 --- a/app/_how-tos/catalog/discover-azure-apis-with-konnect-api.md +++ b/app/_how-tos/catalog/discover-azure-apis-with-konnect-api.md @@ -1,8 +1,8 @@ --- -title: "Discover Azure API Management APIs in Catalog with the {{site.konnect_short_name}} API" +title: "Discover Azure API Management APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API" permalink: /how-to/discover-azure-apis-with-konnect-api/ content_type: how_to -description: Learn how to connect an Azure API Management API to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the API. +description: Learn how to connect an Azure API Management API to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the API. products: - catalog works_on: @@ -15,18 +15,18 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Azure API Management reference url: /catalog/integrations/azure-api-management/ - - text: "Discover Azure API Management APIs with the {{site.konnect_short_name}} UI" + - text: "Discover Azure API Management APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI" url: /how-to/discover-azure-apis-with-konnect-ui/ automated_tests: false tldr: q: How do I discover Azure API Management APIs in {{site.konnect_short_name}}? - a: Install the Azure API Management integration in {{site.konnect_short_name}} and authorize access with OAuth, then link an Azure API to your {{site.konnect_catalog}} service. + a: Install the Azure API Management integration in {{site.konnect_short_name}} and authorize access with OAuth, then link an Azure API to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -39,12 +39,14 @@ prereqs: icon_url: /assets/icons/azure.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the Azure API Management integration {:.info} > **Note:** The Azure API Management integration uses OAuth for authentication and can only be configured through the {{site.konnect_short_name}} UI. -Before you can discover APIs in {{site.konnect_catalog}}, you must configure the Azure API Management integration. +Before you can discover APIs in {{site.konnect_catalog}} Classic, you must configure the Azure API Management integration. 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -59,7 +61,7 @@ Before you can discover APIs in {{site.konnect_catalog}}, you must configure the 1. In the **Instance name** field, enter `azure-api-management-test`. 1. Click **Save**. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your Azure API Management resources: @@ -82,7 +84,7 @@ export AZURE_SERVICE_ID='YOUR-SERVICE-ID' ## List Azure API Management resources -Before you can map your Azure API Management resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from Azure API Management: +Before you can map your Azure API Management resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from Azure API Management: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/discover-azure-apis-with-konnect-ui.md b/app/_how-tos/catalog/discover-azure-apis-with-konnect-ui.md index 75b43fa19a9..39c6a6c70eb 100644 --- a/app/_how-tos/catalog/discover-azure-apis-with-konnect-ui.md +++ b/app/_how-tos/catalog/discover-azure-apis-with-konnect-ui.md @@ -1,8 +1,8 @@ --- -title: "Discover Azure API Management APIs in Catalog with the {{site.konnect_short_name}} UI" +title: "Discover Azure API Management APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI" permalink: /how-to/discover-azure-apis-with-konnect-ui/ content_type: how_to -description: Learn how to connect an Azure API Management API to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the UI. +description: Learn how to connect an Azure API Management API to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the UI. products: - catalog works_on: @@ -13,18 +13,18 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Azure API Management reference url: /catalog/integrations/azure-api-management/ - - text: "Discover Azure API Management APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" + - text: "Discover Azure API Management APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API" url: /how-to/discover-azure-apis-with-konnect-api/ automated_tests: false tldr: q: How do I discover Azure API Management APIs in {{site.konnect_short_name}}? - a: Install the Azure API Management integration in {{site.konnect_short_name}} and authorize access with OAuth, then link an Azure API to your {{site.konnect_catalog}} service. + a: Install the Azure API Management integration in {{site.konnect_short_name}} and authorize access with OAuth, then link an Azure API to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -37,12 +37,14 @@ prereqs: icon_url: /assets/icons/azure.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the Azure API Management integration {:.info} > **Note:** The Azure API Management integration uses OAuth for authentication and can only be configured through the {{site.konnect_short_name}} UI. -Before you can discover APIs in {{site.konnect_catalog}}, you must configure the Azure API Management integration. +Before you can discover APIs in {{site.konnect_catalog}} Classic, you must configure the Azure API Management integration. 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -57,9 +59,9 @@ Before you can discover APIs in {{site.konnect_catalog}}, you must configure the 1. In the **Instance name** field, enter `azure-api-management-test`. 1. Click **Save**. -## Create a {{site.konnect_catalog}} service and map the API resources +## Create a {{site.konnect_catalog}} Classic service and map the API resources -Now that your integration is configured, you can create a {{site.konnect_catalog}} service to map the ingested APIs. +Now that your integration is configured, you can create a {{site.konnect_catalog}} Classic service to map the ingested APIs. {:.info} > In this tutorial, we'll refer to your ingested Azure API Management API as `billing-api`. @@ -73,7 +75,7 @@ Now that your integration is configured, you can create a {{site.konnect_catalog 1. Select `billing-api`. 1. Click **Map 1 Resource**. -Your integration APIs are now discoverable from one {{site.konnect_catalog}} service. +Your integration APIs are now discoverable from one {{site.konnect_catalog}} Classic service. {:.info} > You might need to manually sync your Azure API Management integration for resources to appear. In the {{site.konnect_short_name}} UI, by navigate to the Azure API Management integration you just installed and select **Sync Now** from the **Actions** dropdown menu. diff --git a/app/_how-tos/catalog/install-and-map-datadog-resources.md b/app/_how-tos/catalog/install-and-map-datadog-resources.md index 0b88c88fe8d..ec1319958fd 100644 --- a/app/_how-tos/catalog/install-and-map-datadog-resources.md +++ b/app/_how-tos/catalog/install-and-map-datadog-resources.md @@ -1,8 +1,8 @@ --- -title: Install and map Datadog resources in Catalog +title: Install and map Datadog resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-datadog-resources/ content_type: how_to -description: Learn how to connect Datadog monitors and dashboards to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect Datadog monitors and dashboards to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -13,15 +13,15 @@ automated_tests: false search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Datadog reference url: /catalog/integrations/datadog/ tldr: - q: How do I view Datadog monitors and dashboards in {{site.konnect_catalog}}? - a: Install the Datadog integration in {{site.konnect_short_name}} and authorize it using your API and app keys. Create a {{site.konnect_catalog}} service and associate it with your Datadog resources to display metadata and enable event tracking. + q: How do I view Datadog monitors and dashboards in {{site.konnect_catalog}} Classic? + a: Install the Datadog integration in {{site.konnect_short_name}} and authorize it using your API and app keys. Create a {{site.konnect_catalog}} Classic service and associate it with your Datadog resources to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -50,6 +50,8 @@ prereqs: icon_url: /assets/icons/datadog.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Install and authorize the Datadog integration Before you can ingest resources from Datadog, you must first install and authorize the Datadog integration. @@ -99,7 +101,7 @@ body: Once authorized, monitor and dashboard resources from your Datadog account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your Datadog resources: @@ -123,7 +125,7 @@ export DATADOG_SERVICE_ID='YOUR-SERVICE-ID' ## List Datadog resources -Before you can map your Datadog resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from Datadog: +Before you can map your Datadog resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from Datadog: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-github-resources.md b/app/_how-tos/catalog/install-and-map-github-resources.md index 462182f1aaf..7b66fb2369e 100644 --- a/app/_how-tos/catalog/install-and-map-github-resources.md +++ b/app/_how-tos/catalog/install-and-map-github-resources.md @@ -1,8 +1,8 @@ --- -title: Install and map GitHub resources in Catalog +title: Install and map GitHub resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-github-resources/ content_type: how_to -description: Learn how to connect a GitHub repository to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect a GitHub repository to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,16 +15,16 @@ tags: - integrations - github related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: GitHub reference url: /catalog/integrations/github/ automated_tests: false tldr: - q: How do I connect a GitHub repository to my {{site.konnect_catalog}} service? - a: Install the GitHub integration in {{site.konnect_short_name}} and authorize access to one or more repositories, then link a repository to your {{site.konnect_catalog}} service to display metadata and enable event tracking. + q: How do I connect a GitHub repository to my {{site.konnect_catalog}} Classic service? + a: Install the GitHub integration in {{site.konnect_short_name}} and authorize access to one or more repositories, then link a repository to your {{site.konnect_catalog}} Classic service to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -32,7 +32,7 @@ prereqs: icon_url: /assets/icons/kogo-white.svg - title: GitHub access content: | - To integrate GitHub with {{site.konnect_catalog}}, you need the following: + To integrate GitHub with {{site.konnect_catalog}} Classic, you need the following: * Sufficient permissions in GitHub to authorize third-party applications and install the {{site.konnect_short_name}} GitHub App * A GitHub organization * A repository that you want to pull in to {{site.konnect_short_name}}. You can grant access to either all repositories or selected repositories during the authorization process. @@ -41,6 +41,8 @@ prereqs: icon_url: /assets/icons/github.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Install and authorize the GitHub integration 1. From the **Catalog** in {{site.konnect_short_name}}, select **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -50,7 +52,7 @@ prereqs: The {{site.konnect_short_name}} application can be managed from GitHub as a [GitHub Application](https://docs.github.com/en/apps/using-github-apps/authorizing-github-apps). -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your GitHub resources: @@ -74,7 +76,7 @@ export GITHUB_SERVICE_ID='YOUR-SERVICE-ID' ## List GitHub resources -Before you can map your GitHub resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from GitHub: +Before you can map your GitHub resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from GitHub: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-gitlab-resources.md b/app/_how-tos/catalog/install-and-map-gitlab-resources.md index ed43c44b701..26e46c2e2bf 100644 --- a/app/_how-tos/catalog/install-and-map-gitlab-resources.md +++ b/app/_how-tos/catalog/install-and-map-gitlab-resources.md @@ -1,8 +1,8 @@ --- -title: Install and map self-hosted GitLab resources in Catalog +title: Install and map self-hosted GitLab resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-gitlab-resources/ content_type: how_to -description: Learn how to connect a GitLab project to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect a GitLab project to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,8 +15,8 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: GitLab reference @@ -25,8 +25,8 @@ related_resources: url: /how-to/install-and-map-gitlab-saas-resources/ automated_tests: false tldr: - q: How do I view a self-hosted GitLab project in {{site.konnect_catalog}}? - a: Authorize the GitLab integration in the {{site.konnect_short_name}} UI using self-hosted setup. Create a {{site.konnect_catalog}} service and associate it with your project resource to display metadata and enable event tracking. + q: How do I view a self-hosted GitLab project in {{site.konnect_catalog}} Classic? + a: Authorize the GitLab integration in the {{site.konnect_short_name}} UI using self-hosted setup. Create a {{site.konnect_catalog}} Classic service and associate it with your project resource to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -49,6 +49,8 @@ prereqs: icon_url: /assets/icons/gitlab.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Authorize the self-managed GitLab integration 1. In the {{site.konnect_short_name}} UI, navigate to the [GitLab integration](https://cloud.konghq.com/service-catalog/integrations/gitlab/instances) and click **Add GitLab instance**. @@ -63,7 +65,7 @@ prereqs: Once authorized, resources from your GitLab account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your GitLab resources: @@ -87,7 +89,7 @@ export GITLAB_SERVICE_ID='YOUR-SERVICE-ID' ## List GitLab resources -Before you can map your GitLab resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from GitLab: +Before you can map your GitLab resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from GitLab: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-gitlab-saas-resources.md b/app/_how-tos/catalog/install-and-map-gitlab-saas-resources.md index 9f40337005f..5d1e3415e0a 100644 --- a/app/_how-tos/catalog/install-and-map-gitlab-saas-resources.md +++ b/app/_how-tos/catalog/install-and-map-gitlab-saas-resources.md @@ -1,8 +1,8 @@ --- -title: Install and map SaaS GitLab resources in Catalog +title: Install and map SaaS GitLab resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-gitlab-saas-resources/ content_type: how_to -description: Learn how to connect a SaaS GitLab project to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect a SaaS GitLab project to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,8 +15,8 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: GitLab reference @@ -25,8 +25,8 @@ related_resources: url: /how-to/install-and-map-gitlab-resources/ automated_tests: false tldr: - q: How do I view a SaaS GitLab project in {{site.konnect_catalog}}? - a: Install and authorize the SaaS GitLab integration in the {{site.konnect_short_name}} UI. Create a {{site.konnect_catalog}} service and associate it with your GitLab project to display metadata and enable event tracking. + q: How do I view a SaaS GitLab project in {{site.konnect_catalog}} Classic? + a: Install and authorize the SaaS GitLab integration in the {{site.konnect_short_name}} UI. Create a {{site.konnect_catalog}} Classic service and associate it with your GitLab project to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -38,13 +38,15 @@ prereqs: icon_url: /assets/icons/gitlab.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Authorize the GitLab integration 1. From the **Catalog** in {{site.konnect_short_name}}, select **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. 2. Click **GitLab**, then click **Add GitLab instance**. 3. Select **GitLab (SaaS)**, authorize GitLab to connect your account, and enter `gitlab` for your instance name. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your GitLab resources: @@ -68,7 +70,7 @@ export GITLAB_SERVICE_ID='YOUR-SERVICE-ID' ## List GitLab resources -Before you can map your GitLab resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from GitLab: +Before you can map your GitLab resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from GitLab: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-pagerduty-resources.md b/app/_how-tos/catalog/install-and-map-pagerduty-resources.md index 1a2659f21bc..cdd6de44459 100644 --- a/app/_how-tos/catalog/install-and-map-pagerduty-resources.md +++ b/app/_how-tos/catalog/install-and-map-pagerduty-resources.md @@ -1,8 +1,8 @@ --- -title: Import and map PagerDuty resources in Catalog +title: Import and map PagerDuty resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-pagerduty-resources/ content_type: how_to -description: Learn how to connect PagerDuty services to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect PagerDuty services to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,16 +15,16 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: PagerDuty reference url: /catalog/integrations/pagerduty/ automated_tests: false tldr: - q: How do I view PagerDuty services in {{site.konnect_catalog}}? - a: Install the PagerDuty integration in {{site.konnect_short_name}} and authorize it with both read and write scopes. Create a {{site.konnect_catalog}} service and associate it with your PagerDuty services to display metadata and enable event tracking. + q: How do I view PagerDuty services in {{site.konnect_catalog}} Classic? + a: Install the PagerDuty integration in {{site.konnect_short_name}} and authorize it with both read and write scopes. Create a {{site.konnect_catalog}} Classic service and associate it with your PagerDuty services to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -36,6 +36,8 @@ prereqs: icon_url: /assets/icons/pagerduty.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Authenticate the PagerDuty integration 1. From the **Catalog** in {{site.konnect_short_name}}, select **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -45,7 +47,7 @@ prereqs: Once authorized, resources from your PagerDuty account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your PagerDuty resources: @@ -69,7 +71,7 @@ export PAGERDUTY_SERVICE_ID='YOUR-SERVICE-ID' ## List PagerDuty resources -Before you can map your PagerDuty resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from PagerDuty: +Before you can map your PagerDuty resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from PagerDuty: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-slack-resources.md b/app/_how-tos/catalog/install-and-map-slack-resources.md index 09195714765..54b29c0c5c0 100644 --- a/app/_how-tos/catalog/install-and-map-slack-resources.md +++ b/app/_how-tos/catalog/install-and-map-slack-resources.md @@ -1,8 +1,8 @@ --- -title: Import and map Slack resources in Catalog +title: Import and map Slack resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-slack-resources/ content_type: how_to -description: Learn how to connect Slack channels to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect Slack channels to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,8 +15,8 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Traceable plugin @@ -25,8 +25,8 @@ related_resources: url: /catalog/integrations/slack/ automated_tests: false tldr: - q: How do I view a Slack channel in {{site.konnect_catalog}}? - a: Install the Slack integration in {{site.konnect_short_name}} and authorize it using Slack admin credentials. Create a {{site.konnect_catalog}} service and associate it with your Slack channel to improve visibility and ownership. + q: How do I view a Slack channel in {{site.konnect_catalog}} Classic? + a: Install the Slack integration in {{site.konnect_short_name}} and authorize it using Slack admin credentials. Create a {{site.konnect_catalog}} Classic service and associate it with your Slack channel to improve visibility and ownership. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -38,6 +38,8 @@ prereqs: icon_url: /assets/icons/third-party/slack.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Authorize the Slack integration 1. From the **Catalog** in {{site.konnect_short_name}}, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -47,7 +49,7 @@ prereqs: Once authorized, resources from your Slack account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your Slack resources: @@ -71,7 +73,7 @@ export SLACK_SERVICE_ID='YOUR-SERVICE-ID' ## List Slack resources -Before you can map your Slack resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from Slack: +Before you can map your Slack resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from Slack: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-swaggerhub-resources.md b/app/_how-tos/catalog/install-and-map-swaggerhub-resources.md index 9068791d355..4f4ccfad209 100644 --- a/app/_how-tos/catalog/install-and-map-swaggerhub-resources.md +++ b/app/_how-tos/catalog/install-and-map-swaggerhub-resources.md @@ -1,8 +1,8 @@ --- -title: Import and map SwaggerHub resources in Catalog +title: Import and map SwaggerHub resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-swaggerhub-resources/ content_type: how_to -description: Learn how to connect SwaggerHub API versions to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect SwaggerHub API versions to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,16 +15,16 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: SwaggerHub reference url: /catalog/integrations/swaggerhub/ automated_tests: false tldr: - q: How do I view SwaggerHub API specs in {{site.konnect_catalog}}? - a: Install the SwaggerHub integration in {{site.konnect_short_name}} and authorize using your SwaggerHub API key. Create a {{site.konnect_catalog}} service and associate it with your SwaggerHub API versions to display metadata and enable event tracking. + q: How do I view SwaggerHub API specs in {{site.konnect_catalog}} Classic? + a: Install the SwaggerHub integration in {{site.konnect_short_name}} and authorize using your SwaggerHub API key. Create a {{site.konnect_catalog}} Classic service and associate it with your SwaggerHub API versions to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -41,6 +41,8 @@ prereqs: Additionally, you'll need an [API version](https://support.smartbear.com/swaggerhub/docs/en/manage-apis/versioning.html?sbsearch=API%20Versions0) in SwaggerHub to pull into {{site.konnect_short_name}} as a resource. --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Install and authorize the SwaggerHub integration Before you can ingest resources from SwaggerHub, you must first install and authorize the SwaggerHub integration. @@ -86,7 +88,7 @@ body: Once authorized, resources from your SwaggerHub account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your SwaggerHub resources: @@ -110,7 +112,7 @@ export SWAGGERHUB_SERVICE_ID='YOUR-SERVICE-ID' ## List SwaggerHub resources -Before you can map your SwaggerHub resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from SwaggerHub: +Before you can map your SwaggerHub resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from SwaggerHub: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/install-and-map-traceable-resources.md b/app/_how-tos/catalog/install-and-map-traceable-resources.md index 82e0be1e340..18ad6785aa2 100644 --- a/app/_how-tos/catalog/install-and-map-traceable-resources.md +++ b/app/_how-tos/catalog/install-and-map-traceable-resources.md @@ -1,8 +1,8 @@ --- -title: Import and map Traceable resources in Catalog +title: Import and map Traceable resources in {{site.konnect_catalog}} Classic permalink: /how-to/install-and-map-traceable-resources/ content_type: how_to -description: Learn how to connect Traceable services to your {{site.konnect_catalog}} service in {{site.konnect_short_name}}. +description: Learn how to connect Traceable services to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}}. products: - catalog works_on: @@ -15,8 +15,8 @@ tags: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Traceable plugin @@ -25,8 +25,8 @@ related_resources: url: /catalog/integrations/traceable/ automated_tests: false tldr: - q: How do I view Traceable services in {{site.konnect_catalog}}? - a: Install the Traceable integration in {{site.konnect_short_name}} and authorize it with your Traceable API key. Create a {{site.konnect_catalog}} service and associate it with your Traceable services to display metadata and enable event tracking. + q: How do I view Traceable services in {{site.konnect_catalog}} Classic? + a: Install the Traceable integration in {{site.konnect_short_name}} and authorize it with your Traceable API key. Create a {{site.konnect_catalog}} Classic service and associate it with your Traceable services to display metadata and enable event tracking. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -34,7 +34,7 @@ prereqs: icon_url: /assets/icons/kogo-white.svg - title: Traceable access content: | - You must have an active [Traceable account](https://www.traceable.ai/) and valid API access to connect Traceable services to your {{site.konnect_catalog}} service. You also need a [Traceable Service](https://docs.traceable.ai/docs/domains-services-backends) you can pull into {{site.konnect_short_name}}. + You must have an active [Traceable account](https://www.traceable.ai/) and valid API access to connect Traceable services to your {{site.konnect_catalog}} Classic service. You also need a [Traceable Service](https://docs.traceable.ai/docs/domains-services-backends) you can pull into {{site.konnect_short_name}}. Export your Traceable API key: ```sh @@ -43,6 +43,8 @@ prereqs: icon_url: /assets/icons/traceable.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Install and authorize the Traceable integration Before you can ingest resources from Traceable, you must first install and authorize the Traceable integration. @@ -89,7 +91,7 @@ body: Once authorized, resources from your Traceable account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your Traceable resources: @@ -113,7 +115,7 @@ export TRACEABLE_SERVICE_ID='YOUR-SERVICE-ID' ## List Traceable resources -Before you can map your Traceable resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from Traceable: +Before you can map your Traceable resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from Traceable: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/map-analytics-resources.md b/app/_how-tos/catalog/map-analytics-resources.md index e211a7e164e..ad521f67283 100644 --- a/app/_how-tos/catalog/map-analytics-resources.md +++ b/app/_how-tos/catalog/map-analytics-resources.md @@ -1,8 +1,8 @@ --- -title: Map {{site.observability}} reports in Catalog +title: Map {{site.observability}} reports in {{site.konnect_catalog}} Classic permalink: /how-to/map-analytics-resources/ content_type: how_to -description: Learn how to map {{site.konnect_short_name}} analytics resources in {{site.konnect_catalog}} to visualize {{site.observability}} Reports. +description: Learn how to map {{site.konnect_short_name}} analytics resources in {{site.konnect_catalog}} Classic to visualize {{site.observability}} Reports. products: - catalog works_on: @@ -12,26 +12,28 @@ search_aliases: - service catalog - konnect analytics tldr: - q: How do I map {{site.observability}} reports in {{site.konnect_catalog}}? - a: Create a {{site.konnect_catalog}} service and associate it with your {{site.konnect_short_name}} analytics resources to visualize {{site.observability}} Reports. + q: How do I map {{site.observability}} reports in {{site.konnect_catalog}} Classic? + a: Create a {{site.konnect_catalog}} Classic service and associate it with your {{site.konnect_short_name}} analytics resources to visualize {{site.observability}} Reports. prereqs: inline: - title: "{{site.observability}} reports" content: | - You'll need a [{{site.observability}} report](https://cloud.konghq.com/analytics/reports) to ingest in {{site.konnect_catalog}} as resources. + You'll need a [{{site.observability}} report](https://cloud.konghq.com/analytics/reports) to ingest in {{site.konnect_catalog}} Classic as resources. icon_url: /assets/icons/analytics.svg related_resources: - text: "{{site.observability}} integration" url: /catalog/integrations/konnect-analytics/ - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "{{site.konnect_catalog}} integrations" url: /catalog/integrations/ --- -## Create a service in {{site.konnect_catalog}} +{% include_cached catalog/catalog-classic-banner.md %} -In this tutorial, you'll map Reports from {{site.observability}} to a service in {{site.konnect_catalog}}. Because the {{site.observability}} integration is built-in, you don't need to install or authorize it like other {{site.konnect_catalog}} integrations. +## Create a service in {{site.konnect_catalog}} Classic + +In this tutorial, you'll map Reports from {{site.observability}} to a service in {{site.konnect_catalog}} Classic. Because the {{site.observability}} integration is built-in, you don't need to install or authorize it like other {{site.konnect_catalog}} Classic integrations. Create a service that you'll map to your {{site.observability}} resources: @@ -47,7 +49,7 @@ body: {% endkonnect_api_request %} -Export the {{site.konnect_catalog}} service ID: +Export the {{site.konnect_catalog}} Classic service ID: ```sh export SERVICE_ID='YOUR-SERVICE-ID' @@ -55,7 +57,7 @@ export SERVICE_ID='YOUR-SERVICE-ID' ## List {{site.observability}} resources -Before you can map a resource to {{site.konnect_catalog}}, you first need to find the resources that are pulled in from {{site.observability}}: +Before you can map a resource to {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from {{site.observability}}: {% konnect_api_request %} @@ -72,7 +74,7 @@ Export the resource ID you want to map to the service: export ANALYTICS_RESOURCE_ID='YOUR-RESOURCE-ID' ``` -## Map resources to a {{site.konnect_catalog}} service +## Map resources to a {{site.konnect_catalog}} Classic service Now, you can map the {{site.observability}} resource to the service: diff --git a/app/_how-tos/catalog/map-api-gateway-resources.md b/app/_how-tos/catalog/map-api-gateway-resources.md index 99904508cc6..70bbc7ba5b8 100644 --- a/app/_how-tos/catalog/map-api-gateway-resources.md +++ b/app/_how-tos/catalog/map-api-gateway-resources.md @@ -1,8 +1,8 @@ --- -title: Map API Gateway Services in Catalog +title: Map API Gateway Services in {{site.konnect_catalog}} Classic permalink: /how-to/map-api-gateway-resources/ content_type: how_to -description: Learn how to map Gateway Services from {{site.konnect_short_name}} API Gateway in {{site.konnect_catalog}} to visualize services across multiple Control Planes. +description: Learn how to map Gateway Services from {{site.konnect_short_name}} API Gateway in {{site.konnect_catalog}} Classic to visualize services across multiple Control Planes. products: - gateway - catalog @@ -15,8 +15,8 @@ entities: search_aliases: - service catalog tldr: - q: How do I map Gateway Services in {{site.konnect_catalog}}? - a: Create a {{site.konnect_catalog}} service and associate it with your API Gateway resources to visualize Services across multiple Control Planes. + q: How do I map Gateway Services in {{site.konnect_catalog}} Classic? + a: Create a {{site.konnect_catalog}} Classic service and associate it with your API Gateway resources to visualize Services across multiple Control Planes. prereqs: entities: services: @@ -24,15 +24,17 @@ prereqs: related_resources: - text: API Gateway integration url: /catalog/integrations/api-gateway/ - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "{{site.konnect_catalog}} integrations" url: /catalog/integrations/ --- -## Create a service in {{site.konnect_catalog}} +{% include_cached catalog/catalog-classic-banner.md %} -In this tutorial, you'll map Gateway Services from API Gateway to a service in {{site.konnect_catalog}}. Because the API Gateway integration is built-in, you don't need to install or authorize it like other {{site.konnect_catalog}} integrations. +## Create a service in {{site.konnect_catalog}} Classic + +In this tutorial, you'll map Gateway Services from API Gateway to a service in {{site.konnect_catalog}} Classic. Because the API Gateway integration is built-in, you don't need to install or authorize it like other {{site.konnect_catalog}} Classic integrations. Create a service that you'll map to your API Gateway resources: @@ -48,7 +50,7 @@ body: {% endkonnect_api_request %} -Export the {{site.konnect_catalog}} service ID: +Export the {{site.konnect_catalog}} Classic service ID: ```sh export SERVICE_ID='YOUR-SERVICE-ID' @@ -56,7 +58,7 @@ export SERVICE_ID='YOUR-SERVICE-ID' ## List API Gateway resources -Before you can map a resource to {{site.konnect_catalog}}, you first need to find the resources that are pulled in from API Gateway: +Before you can map a resource to {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from API Gateway: {% konnect_api_request %} @@ -73,7 +75,7 @@ Export the resource ID you want to map to the service: export API_GATEWAY_RESOURCE_ID='YOUR-RESOURCE-ID' ``` -## Map resources to a {{site.konnect_catalog}} service +## Map resources to a {{site.konnect_catalog}} Classic service Now, you can map the API Gateway resource to the service: diff --git a/app/_how-tos/catalog/map-service-mesh-resources.md b/app/_how-tos/catalog/map-service-mesh-resources.md index 511e0b3a172..81c9d52df41 100644 --- a/app/_how-tos/catalog/map-service-mesh-resources.md +++ b/app/_how-tos/catalog/map-service-mesh-resources.md @@ -1,8 +1,8 @@ --- -title: Map Service Mesh services in Catalog +title: Map Service Mesh services in {{site.konnect_catalog}} Classic permalink: /how-to/map-service-mesh-resources/ content_type: how_to -description: Learn how to map Service Mesh resources in {{site.konnect_catalog}} to gain visibility into how the service is deployed across meshes and zones. +description: Learn how to map Service Mesh resources in {{site.konnect_catalog}} Classic to gain visibility into how the service is deployed across meshes and zones. products: - catalog works_on: @@ -12,26 +12,28 @@ entities: [] search_aliases: - service catalog tldr: - q: How do I map Service Mesh services in {{site.konnect_catalog}}? - a: Create a {{site.konnect_catalog}} service and associate it with your Service Mesh resources to visualize meshes. + q: How do I map Service Mesh services in {{site.konnect_catalog}} Classic? + a: Create a {{site.konnect_catalog}} Classic service and associate it with your Service Mesh resources to visualize meshes. prereqs: inline: - title: "{{site.mesh_product_name}} services" content: | - You'll need a [Service Mesh service](https://cloud.konghq.com/mesh-manager) to ingest in {{site.konnect_catalog}} as resources. + You'll need a [Service Mesh service](https://cloud.konghq.com/mesh-manager) to ingest in {{site.konnect_catalog}} Classic as resources. icon_url: /assets/icons/mesh.svg related_resources: - text: "Service Mesh integration" url: /catalog/integrations/service-mesh/ - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "{{site.konnect_catalog}} integrations" url: /catalog/integrations/ --- -## Create a service in {{site.konnect_catalog}} +{% include_cached catalog/catalog-classic-banner.md %} -In this tutorial, you'll map services from {{site.mesh_product_name}} to a service in {{site.konnect_catalog}}. Because the Service Mesh integration is built-in, you don't need to install or authorize it like other {{site.konnect_catalog}} integrations. +## Create a service in {{site.konnect_catalog}} Classic + +In this tutorial, you'll map services from {{site.mesh_product_name}} to a service in {{site.konnect_catalog}} Classic. Because the Service Mesh integration is built-in, you don't need to install or authorize it like other {{site.konnect_catalog}} Classic integrations. Create a service that you'll map to your Service Mesh resources: @@ -47,7 +49,7 @@ body: {% endkonnect_api_request %} -Export the {{site.konnect_catalog}} service ID: +Export the {{site.konnect_catalog}} Classic service ID: ```sh export SERVICE_ID='YOUR-SERVICE-ID' @@ -55,7 +57,7 @@ export SERVICE_ID='YOUR-SERVICE-ID' ## List Service Mesh resources -Before you can map a resource to {{site.konnect_catalog}}, you first need to find the resources that are pulled in: +Before you can map a resource to {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in: {% konnect_api_request %} @@ -72,7 +74,7 @@ Export the resource ID you want to map to the service: export MESH_RESOURCE_ID='YOUR-RESOURCE-ID' ``` -## Map resources to a {{site.konnect_catalog}} service +## Map resources to a {{site.konnect_catalog}} Classic service Now, you can map the Service Mesh resource to the service: diff --git a/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-api.md b/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-api.md index 576bcddf15e..7b8beb17df1 100644 --- a/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-api.md +++ b/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-api.md @@ -1,8 +1,8 @@ --- -title: Monitor Dynatrace classic SLOs in Catalog with the Konnect API +title: Monitor Dynatrace classic SLOs in {{site.konnect_catalog}} Classic with the Konnect API permalink: /how-to/monitor-dynatrace-slos-with-konnect-api/ content_type: how_to -description: Learn how to connect a Dynatrace classic SLO to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the API. +description: Learn how to connect a Dynatrace classic SLO to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the API. products: - catalog works_on: @@ -17,20 +17,20 @@ search_aliases: - SLO - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Dynatrace reference url: /catalog/integrations/dynatrace/ - - text: "Monitor Dynatrace classic SLOs {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI" + - text: "Monitor Dynatrace classic SLOs in {{site.konnect_catalog}} Classic with the Konnect UI" url: /how-to/monitor-dynatrace-slos-with-konnect-ui/ - text: Set up Dynatrace with OpenTelemetry url: /how-to/set-up-dynatrace-with-otel/ automated_tests: false tldr: q: How do I monitor Dynatrace classic service-level objects in {{site.konnect_short_name}}? - a: Install the Dynatrace integration in {{site.konnect_short_name}} and authorize access with your Dynatrace URL and personal access token (with `slo.read` permissions), then link an SLO to your {{site.konnect_catalog}} service. + a: Install the Dynatrace integration in {{site.konnect_short_name}} and authorize access with your Dynatrace URL and personal access token (with `slo.read` permissions), then link an SLO to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -54,9 +54,11 @@ prereqs: icon_url: /assets/icons/third-party/dynatrace.png --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the Dynatrace integration -Before you can discover SLOs in {{site.konnect_catalog}}, you must configure the Dynatrace integration. +Before you can discover SLOs in {{site.konnect_catalog}} Classic, you must configure the Dynatrace integration. First, install the Dynatrace integration: @@ -100,7 +102,7 @@ body: Once authorized, resources from your Dynatrace account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your Dynatrace resources: @@ -124,7 +126,7 @@ export DYNATRACE_SERVICE_ID='YOUR-SERVICE-ID' ## List Dynatrace resources -Before you can map your Dynatrace resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from Dynatrace: +Before you can map your Dynatrace resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from Dynatrace: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-ui.md b/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-ui.md index e7b37b42b9a..e4ffee8e37d 100644 --- a/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-ui.md +++ b/app/_how-tos/catalog/monitor-dynatrace-slos-with-konnect-ui.md @@ -1,8 +1,8 @@ --- -title: Monitor Dynatrace classic SLOs in Catalog with the Konnect UI +title: Monitor Dynatrace classic SLOs in {{site.konnect_catalog}} Classic with the Konnect UI permalink: /how-to/monitor-dynatrace-slos-with-konnect-ui/ content_type: how_to -description: Learn how to connect a Dynatrace classic SLO to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the UI. +description: Learn how to connect a Dynatrace classic SLO to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the UI. products: - catalog works_on: @@ -15,20 +15,20 @@ search_aliases: - SLO - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Dynatrace reference url: /catalog/integrations/dynatrace/ - - text: "Monitor Dynatrace classic SLOs {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" + - text: "Monitor Dynatrace classic SLOs in {{site.konnect_catalog}} Classic with the Konnect API" url: /how-to/monitor-dynatrace-slos-with-konnect-api/ - text: Set up Dynatrace with OpenTelemetry url: /how-to/set-up-dynatrace-with-otel/ automated_tests: false tldr: q: How do I monitor Dynatrace classic service-level objects in {{site.konnect_short_name}}? - a: Install the Dynatrace integration in {{site.konnect_short_name}} and authorize access with your Dynatrace URL and personal access token (with `slo.read` permissions), then link an SLO to your {{site.konnect_catalog}} service. + a: Install the Dynatrace integration in {{site.konnect_short_name}} and authorize access with your Dynatrace URL and personal access token (with `slo.read` permissions), then link an SLO to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -46,9 +46,11 @@ prereqs: icon_url: /assets/icons/third-party/dynatrace.png --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the Dynatrace integration -Before you can discover APIs in {{site.konnect_catalog}}, you must configure the Dynatrace integration. +Before you can discover APIs in {{site.konnect_catalog}} Classic, you must configure the Dynatrace integration. 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -60,9 +62,9 @@ Before you can discover APIs in {{site.konnect_catalog}}, you must configure the 1. In the **Instance name** field, enter `dynatrace`. 1. Click **Save**. -## Create a {{site.konnect_catalog}} service and map the SLO resources +## Create a {{site.konnect_catalog}} Classic service and map the SLO resources -Now that your integration is configured, you can create a {{site.konnect_catalog}} service to map the ingested SLOs. +Now that your integration is configured, you can create a {{site.konnect_catalog}} Classic service to map the ingested SLOs. {:.info} > In this tutorial, we'll refer to your ingested Dynatrace SLO as `billing-slo`. @@ -77,7 +79,7 @@ Now that your integration is configured, you can create a {{site.konnect_catalog 1. Select `billing-slo`. 1. Click **Map 1 Resource**. -Your integration SLOs are now discoverable from one {{site.konnect_catalog}} service. +Your integration SLOs are now discoverable from one {{site.konnect_catalog}} Classic service. {:.info} > You might need to manually sync your Dynatrace integration for resources to appear. From the {{site.konnect_short_name}} UI by navigating to the Dynatrace integration you just installed and selecting **Sync Now** from the **Actions** dropdown menu. diff --git a/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-api.md b/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-api.md index 829315f6619..d268798f937 100644 --- a/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-api.md +++ b/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-api.md @@ -1,8 +1,8 @@ --- -title: Monitor SonarQube projects in Catalog with the Konnect API +title: Monitor SonarQube projects in {{site.konnect_catalog}} Classic with the Konnect API permalink: /how-to/monitor-sonarqube-projects-with-konnect-api/ content_type: how_to -description: Learn how to connect a SonarQube project to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the API. +description: Learn how to connect a SonarQube project to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the API. products: - catalog works_on: @@ -16,18 +16,18 @@ search_aliases: - projects - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: SonarQube reference url: /catalog/integrations/sonarqube/ - - text: "Monitor SonarQube projects {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI" + - text: "Monitor SonarQube projects in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI" url: /how-to/monitor-sonarqube-projects-with-konnect-ui/ automated_tests: false tldr: q: How do I monitor SonarQube projects in {{site.konnect_short_name}}? - a: Install the SonarQube integration in {{site.konnect_short_name}} and authorize access with your SonarQube personal access token, then link a project to your {{site.konnect_catalog}} service. + a: Install the SonarQube integration in {{site.konnect_short_name}} and authorize access with your SonarQube personal access token, then link a project to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -48,9 +48,11 @@ prereqs: icon_url: /assets/icons/third-party/sonarqube.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the SonarQube integration -Before you can discover [SonarQube projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects) in {{site.konnect_catalog}}, you must configure the SonarQube integration. +Before you can discover [SonarQube projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects) in {{site.konnect_catalog}} Classic, you must configure the SonarQube integration. First, install the SonarQube integration: @@ -93,7 +95,7 @@ body: Once authorized, resources from your SonarQube account will be discoverable in the UI. -## Create a service in {{site.konnect_catalog}} +## Create a service in {{site.konnect_catalog}} Classic Create a service that you'll map to your SonarQube resources: @@ -117,7 +119,7 @@ export SONARQUBE_SERVICE_ID='YOUR-SERVICE-ID' ## List SonarQube resources -Before you can map your SonarQube resources to a service in {{site.konnect_catalog}}, you first need to find the resources that are pulled in from SonarQube: +Before you can map your SonarQube resources to a service in {{site.konnect_catalog}} Classic, you first need to find the resources that are pulled in from SonarQube: {% konnect_api_request %} diff --git a/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-ui.md b/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-ui.md index 85f43f0b413..96dc12188c5 100644 --- a/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-ui.md +++ b/app/_how-tos/catalog/monitor-sonarqube-projects-with-konnect-ui.md @@ -1,8 +1,8 @@ --- -title: Monitor SonarQube projects in Catalog with the {{site.konnect_short_name}} UI +title: Monitor SonarQube projects in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI permalink: /how-to/monitor-sonarqube-projects-with-konnect-ui/ content_type: how_to -description: Learn how to connect a SonarQube project to your {{site.konnect_catalog}} service in {{site.konnect_short_name}} using the UI. +description: Learn how to connect a SonarQube project to your {{site.konnect_catalog}} Classic service in {{site.konnect_short_name}} using the UI. products: - catalog works_on: @@ -14,18 +14,18 @@ search_aliases: - project - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: SonarQube reference url: /catalog/integrations/sonarqube/ - - text: "Monitor SonarQube projects {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" + - text: "Monitor SonarQube projects in {{site.konnect_catalog}} Classic with the Konnect API" url: /how-to/monitor-sonarqube-projects-with-konnect-api/ automated_tests: false tldr: q: How do I monitor SonarQube projects in {{site.konnect_short_name}}? - a: Install the SonarQube integration in {{site.konnect_short_name}} and authorize access with your SonarQube personal access token, then link a project to your {{site.konnect_catalog}} service. + a: Install the SonarQube integration in {{site.konnect_short_name}} and authorize access with your SonarQube personal access token, then link a project to your {{site.konnect_catalog}} Classic service. prereqs: inline: - title: "{{site.konnect_short_name}} roles" @@ -41,9 +41,11 @@ prereqs: icon_url: /assets/icons/third-party/sonarqube.svg --- +{% include_cached catalog/catalog-classic-banner.md %} + ## Configure the SonarQube integration -Before you can discover [SonarQube projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects) in {{site.konnect_catalog}}, you must configure the SonarQube integration. +Before you can discover [SonarQube projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects) in {{site.konnect_catalog}} Classic, you must configure the SonarQube integration. 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. @@ -54,9 +56,9 @@ Before you can discover [SonarQube projects](https://docs.sonarsource.com/sonarq 1. In the **Instance name** field, enter `sonarqube`. 1. Click **Save**. -## Create a {{site.konnect_catalog}} service and map the SLO resources +## Create a {{site.konnect_catalog}} Classic service and map the SLO resources -Now that your integration is configured, you can create a {{site.konnect_catalog}} service to map the ingested projects. +Now that your integration is configured, you can create a {{site.konnect_catalog}} Classic service to map the ingested projects. {:.info} > In this tutorial, we'll refer to your ingested SonarQube project as `billing-project`. @@ -71,7 +73,7 @@ Now that your integration is configured, you can create a {{site.konnect_catalog 1. Select `billing-project`. 1. Click **Map 1 Resource**. -Your integration projects are now discoverable from one {{site.konnect_catalog}} service. +Your integration projects are now discoverable from one {{site.konnect_catalog}} Classic service. {:.info} > You may need to manually sync your SonarQube integration for resources to appear. From the {{site.konnect_short_name}} UI by navigating to the SonarQube integration you just installed and selecting **Sync Now** from the **Actions** dropdown menu. diff --git a/app/_how-tos/dev-portal/package-apis-with-dev-portal.md b/app/_how-tos/dev-portal/package-apis-with-dev-portal.md index 9fab123219e..0ca406ea392 100644 --- a/app/_how-tos/dev-portal/package-apis-with-dev-portal.md +++ b/app/_how-tos/dev-portal/package-apis-with-dev-portal.md @@ -47,7 +47,12 @@ prereqs: - title: Dev Portal APIs content: | To complete this guide, you'll need an API in Catalog: + 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. + 1. Click the **APIs** tab. + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **APIs** in the sidebar instead. 1. Click [**New API**](https://cloud.konghq.com/apis/create). 1. In the **API name** field, enter `MyAPI`. 1. Click **Create**. @@ -274,7 +279,12 @@ You can compose [API packages](/catalog/api-packaging/) from existing APIs in De To allow developers to consume your API, you must first link an API Gateway and control plane to your API. Operations from your API's OpenAPI spec should overlap with Routes to ensure requests will be routed to the correct Service. Gateway routing configuration isn't directly modified by adding operations. + 1. In the {{site.konnect_short_name}} sidebar, click [**Catalog**](https://cloud.konghq.com/apis/). + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **APIs** in the sidebar instead. + 1. Click **MyAPI**. 1. Click the **Gateway** tab. 1. Click **Link gateway**. @@ -295,6 +305,9 @@ The Gateway configuration isn't directly modified, so any unmatched operations w 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. Click the **API packages** tab. + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **API packages** in the sidebar instead. 1. Click **Create API package**. 1. In the **API package name** field, enter `Company package`. 1. Enable the Package rate limit. @@ -312,8 +325,12 @@ The Gateway configuration isn't directly modified, so any unmatched operations w ## Publish API packages to Dev Portal Now you can make the API packages available to developers by publishing them to a Dev Portal. + 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. 1. Click the **API packages** tab. + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **API packages** in the sidebar instead. 1. Click **Company package**. 1. Click **Publish API**. 1. From the **Portal** dropdown menu, select your Dev Portal. diff --git a/app/_includes/catalog/catalog-classic-banner.md b/app/_includes/catalog/catalog-classic-banner.md new file mode 100644 index 00000000000..a8905f12b83 --- /dev/null +++ b/app/_includes/catalog/catalog-classic-banner.md @@ -0,0 +1,2 @@ +{:.warning} +> You're viewing the {{site.konnect_catalog}} Classic docs. To see the new {{site.konnect_catalog}} experience, see the [{{site.konnect_catalog}} documentation](/catalog/). diff --git a/app/_indices/catalog.yaml b/app/_indices/catalog.yaml index 60f997442d9..7062685f6b7 100644 --- a/app/_indices/catalog.yaml +++ b/app/_indices/catalog.yaml @@ -1,23 +1,34 @@ title: "Catalog Documentation" description: Index containing all documentation for {{site.konnect_catalog}}. -sections: - - title: Overview - items: - - path: /catalog/ - - title: APIs - items: - - path: /service-catalog/apis/ - - path: /catalog/api-packaging/ - - path: /how-to/automate-api-catalog/ - - path: /how-to/automate-api-catalog-with-terraform/ - - path: /how-to/discover-and-govern-apis-with-service-catalog/ - - path: /how-to/package-apis-with-dev-portal/ - - title: Services and scorecards - items: - - path: /catalog/scorecards/ - - path: /catalog/services/ - - title: Integrations - items: - - path: /catalog/integrations/ - - path: /catalog/integrations/**/* - auto_exclude: true +groups: + - sections: + - title: Overview + items: + - path: /catalog/ + - title: APIs + items: + - path: /service-catalog/apis/ + - path: /catalog/api-packaging/ + - path: /how-to/automate-api-catalog/ + - path: /how-to/automate-api-catalog-with-terraform/ + - path: /how-to/package-apis-with-dev-portal/ + - title: "{{site.konnect_catalog}} Classic" + sections: + - title: Overview + items: + - path: /catalog-classic/ + - title: Services and scorecards + items: + - path: /catalog/scorecards/ + - path: /catalog/services/ + - title: Integrations + items: + - path: /catalog/integrations/ + - path: /catalog/integrations/**/* + auto_exclude: true + - title: How-tos + items: + - path: /how-to/discover-and-govern-apis-with-service-catalog/ + - title: MCP Registry + items: + - path: /catalog/mcp-registry/ diff --git a/app/_landing_pages/catalog-classic.yaml b/app/_landing_pages/catalog-classic.yaml new file mode 100644 index 00000000000..fc858fc8e16 --- /dev/null +++ b/app/_landing_pages/catalog-classic.yaml @@ -0,0 +1,150 @@ +metadata: + title: "{{site.konnect_short_name}} {{site.konnect_catalog}} Classic" + content_type: landing_page + products: + - catalog + description: Learn how to track and manage services across your organization with the {{site.konnect_short_name}} {{site.konnect_catalog}} Classic. + tags: + - governance + search_aliases: + - service catalog + +rows: + - header: + type: h1 + text: "{{site.konnect_short_name}} {{site.konnect_catalog}} Classic" + sub_text: "A centralized catalog of all services running in your {{site.konnect_short_name}} organization" + + - columns: + - blocks: + - type: text + config: | + {% include_cached catalog/catalog-classic-banner.md %} + + - columns: + - blocks: + - type: structured_text + config: + header: + text: "What is the {{site.konnect_short_name}} {{site.konnect_catalog}} Classic?" + blocks: + - type: text + text: | + {{site.konnect_catalog}} Classic provides a centralized catalog of all services and APIs running in your organization. + By integrating with internal applications, like API Gateway and Service Mesh, and external tools, like GitHub and PagerDuty, + it offers a 360-degree overview of your services, including: + - type: unordered_list + items: + - Service ownership details + - Upstream and downstream dependencies + - Associated code repositories and CI/CD pipelines + - API gateway and service mesh mappings + - Comprehensive API and MCP server catalog + + - header: + type: h2 + text: "Create your catalog" + columns: + - blocks: + - type: card + config: + title: APIs + description: | + Create, discover, and govern APIs and specs. + Catalog serves as a central repository for your APIs, services, and the documentation files associated with them. + icon: /assets/icons/api.svg + ctas: + - text: APIs reference + url: "/catalog/apis/" + - text: API packages + url: /catalog/api-packaging/ + - text: Create an API catalog with the {{site.konnect_short_name}} API + url: "/how-to/automate-api-catalog/" + - text: Create an API catalog with Terraform + url: "/how-to/automate-api-catalog-with-terraform/" + - text: Discover and govern APIs + url: /how-to/discover-and-govern-apis-with-service-catalog/ + - blocks: + - type: card + config: + title: "Services" + description: | + Discover the systems that power your APIs—like microservices or backends—and centralize them for a complete view of your API infrastructure. + icon: /assets/icons/linked-services.svg + cta: + text: Learn about {{site.konnect_catalog}} services + url: /catalog/services/ + - blocks: + - type: card + config: + title: MCP Registry (tech preview) + description: | + Discover and connect MCP servers to {{site.konnect_short_name}} {{site.konnect_catalog}}. + icon: /assets/icons/mcp.svg + cta: + text: Enable in {{site.konnect_short_name}} Labs. + url: /catalog/mcp-registry/ + - header: + type: h2 + text: "Explore more features" + columns: + - blocks: + - type: card + config: + title: Integrations + description: | + Connect external tools like GitHub, PagerDuty, and CI/CD pipelines to map services, dependencies, and metadata. + icon: /assets/icons/plug.svg + cta: + text: See all integrations + url: /catalog/integrations/ + - blocks: + - type: card + config: + title: Scorecards + description: | + Monitor compliance, security, and best practices across services using automated scorecards. + icon: /assets/icons/data-object.svg + cta: + text: Learn about scorecards + url: /catalog/scorecards/ + - header: + type: h2 + text: "Migrate to the new Catalog" + columns: + - blocks: + - type: structured_text + config: + blocks: + - type: text + text: | + The [new {{site.konnect_catalog}} experience](/catalog/) is a unified, platform-level home for your interfaces. Here's how it compares + to {{site.konnect_catalog}} Classic: + + * **AI Models**: The new {{site.konnect_catalog}} adds support for AI Models as a first-class interface, with more interface + types coming. + * **Continued support for APIs**: APIs and API packages work the same way in both experiences, APIs and API packages migrate over. + + Services, Scorecards, Integrations, and the MCP Registry are only compatible with {{site.konnect_catalog}} Classic. + + An Org Admin can migrate to the new {{site.konnect_catalog}} experience by enabling the New Catalog + in **Manage organization** > **Settings** > **Catalog**. + + Your APIs and API packages migrate to the new {{site.konnect_catalog}}. Services, Scorecards, and Integrations data isn't deleted, + but becomes inaccessible in the UI after migrating. You can still manage these and access their data by using the API. + + - header: + type: h2 + text: "Frequently asked questions" + columns: + - blocks: + - type: faqs + config: + - q: "How do I view service health and status?" + a: "Go to **Services** in {{site.konnect_catalog}} Classic and select a service to view detailed health and status information." + - q: "How can I identify available resources for mapping?" + a: "Visit the **Resources** page in {{site.konnect_catalog}} Classic to see all available ingested resources." + - q: "What if I notice discrepancies in {{site.konnect_catalog}} data?" + a: "Check integration settings, verify connected tools, and ensure data synchronization is working correctly." + - q: "Can I control access to specific {{site.konnect_catalog}} data?" + a: "Yes, access can be managed through [teams and roles](/konnect-platform/teams-and-roles/)." diff --git a/app/_landing_pages/catalog.yaml b/app/_landing_pages/catalog.yaml index 46849fd6539..42f9196d6b0 100644 --- a/app/_landing_pages/catalog.yaml +++ b/app/_landing_pages/catalog.yaml @@ -3,37 +3,41 @@ metadata: content_type: landing_page products: - catalog - description: Learn how to track and manage services across your organization with the {{site.konnect_short_name}} {{site.konnect_catalog}}. + description: Learn how to create, discover, and govern the interfaces your organization publishes and consumes with {{site.konnect_short_name}} {{site.konnect_catalog}}. tags: - governance search_aliases: - service catalog + - api catalog rows: - header: type: h1 text: "{{site.konnect_short_name}} {{site.konnect_catalog}}" - sub_text: "A centralized catalog of all services running in your {{site.konnect_short_name}} organization" - + sub_text: "A platform-level home for the interfaces your organization publishes and consumes" + + - columns: + - blocks: + - type: text + config: | + {:.info} + > Looking for {{site.konnect_catalog}} Classic? + > See the [{{site.konnect_catalog}} Classic documentation](/catalog-classic/). + - columns: - blocks: - type: structured_text config: header: - text: "What is the {{site.konnect_short_name}} {{site.konnect_catalog}}?" + text: "What is {{site.konnect_short_name}} {{site.konnect_catalog}}?" blocks: - type: text text: | - {{site.konnect_catalog}} provides a centralized catalog of all services and APIs running in your organization. - By integrating with internal applications, like API Gateway and Service Mesh, and external tools, like GitHub and PagerDuty, - it offers a 360-degree overview of your services, including: - - type: unordered_list - items: - - Service ownership details - - Upstream and downstream dependencies - - Associated code repositories and CI/CD pipelines - - API gateway and service mesh mappings - - Comprehensive API and MCP server catalog + {{site.konnect_catalog}} is where your organization's interfaces live: APIs, API packages, and AI Models today, with more interface types + coming. Instead of digging through individual products to find what already exists, {{site.konnect_catalog}} gives you a + platform-level home for creating, describing, and governing them. + + - header: type: h2 @@ -45,63 +49,35 @@ rows: title: APIs description: | Create, discover, and govern APIs and specs. - Catalog serves as a central repository for your APIs, services, and the documentation files associated with them. + Catalog serves as a central repository for your APIs and the documentation files associated with them. icon: /assets/icons/api.svg ctas: - text: APIs reference url: "/catalog/apis/" - - text: API packages - url: /catalog/api-packaging/ - text: Create an API catalog with the {{site.konnect_short_name}} API url: "/how-to/automate-api-catalog/" - text: Create an API catalog with Terraform url: "/how-to/automate-api-catalog-with-terraform/" - - text: Discover and govern APIs - url: /how-to/discover-and-govern-apis-with-service-catalog/ - - blocks: - - type: card - config: - title: "Services" - description: | - Discover the systems that power your APIs—like microservices or backends—and centralize them for a complete view of your API infrastructure. - icon: /assets/icons/linked-services.svg - cta: - text: Learn about {{site.konnect_catalog}} services - url: /catalog/services/ - - blocks: - - type: card - config: - title: MCP Registry (tech preview) - description: | - Discover and connect MCP servers to {{site.konnect_short_name}} {{site.konnect_catalog}}. - icon: /assets/icons/mcp.svg - cta: - text: Enable in {{site.konnect_short_name}} Labs. - url: /catalog/mcp-registry/ - - header: - type: h2 - text: "Explore more features" - columns: - blocks: - type: card config: - title: Integrations + title: "API packages" description: | - Connect external tools like GitHub, PagerDuty, and CI/CD pipelines to map services, dependencies, and metadata. - icon: /assets/icons/plug.svg + Compose API packages from existing operations to serve specific partners or use cases. + icon: /assets/icons/api.svg cta: - text: See all integrations - url: /catalog/integrations/ + text: API packages reference + url: /catalog/api-packaging/ - blocks: - type: card config: - title: Scorecards + title: "AI Models" description: | - Monitor compliance, security, and best practices across services using automated scorecards. - icon: /assets/icons/data-object.svg + Model your organization's AI models as first-class interfaces in {{site.konnect_catalog}}. + icon: /assets/icons/brain.svg cta: - text: Learn about scorecards - url: /catalog/scorecards/ + text: Learn about AI Models + url: /catalog/ai-models/ - header: type: h2 text: "Frequently asked questions" @@ -109,11 +85,9 @@ rows: - blocks: - type: faqs config: - - q: "How do I view service health and status?" - a: "Go to **Services** in the {{site.konnect_catalog}} and select a service to view detailed health and status information." - - q: "How can I identify available resources for mapping?" - a: "Visit the **Resources** page in the {{site.konnect_catalog}} to see all available ingested resources." - - q: "What if I notice discrepancies in {{site.konnect_catalog}} data?" - a: "Check integration settings, verify connected tools, and ensure data synchronization is working correctly." + - q: "What's different between {{site.konnect_catalog}} and {{site.konnect_catalog}} Classic?" + a: "{{site.konnect_catalog}} is the unified, platform-level experience for APIs, API packages, and AI Models today, with more interface types coming. {{site.konnect_catalog}} Classic remains available with Services, Scorecards, Integrations, and MCP Registry. See [Migrate to the new Catalog](/catalog-classic/#migrate-to-the-new-catalog) for how to move to the new experience." + - q: "What happened to Services, Integrations, and Scorecards?" + a: "Those features are compatible with {{site.konnect_catalog}} Classic. See the [{{site.konnect_catalog}} Classic documentation](/catalog-classic/)." - q: "Can I control access to specific {{site.konnect_catalog}} data?" a: "Yes, access can be managed through [teams and roles](/konnect-platform/teams-and-roles/)." diff --git a/app/_landing_pages/catalog/integrations.yaml b/app/_landing_pages/catalog/integrations.yaml index 00583b741c4..a0c81a911c0 100644 --- a/app/_landing_pages/catalog/integrations.yaml +++ b/app/_landing_pages/catalog/integrations.yaml @@ -4,7 +4,7 @@ metadata: products: - catalog breadcrumbs: - - /catalog/ + - /catalog-classic/ description: Integrate third-party applications into your {{site.konnect_short_name}} organization. tags: - integrations diff --git a/app/catalog/api-packaging.md b/app/catalog/api-packaging.md index 3726ffa8043..f55a04c5be3 100644 --- a/app/catalog/api-packaging.md +++ b/app/catalog/api-packaging.md @@ -168,6 +168,9 @@ To package APIs with Dev Portal, you need: 1. In {{site.konnect_short_name}}, click **Catalog**. 1. Click the **API packages** tab. + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **API packages** in the sidebar instead. 1. Click **Create API package**. 1. In the **API package name** field, enter a name for your package. 1. Enable the Package rate limit and configure your rate limit. @@ -184,6 +187,9 @@ The image must be a PNG, JPG, or SVG image under 500 KB that’s no larger than 1. In {{site.konnect_short_name}}, click **Catalog**. 1. Click the **API packages** tab. + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **API packages** in the sidebar instead. 1. Click your API package. 1. Click **Publish API**. 1. From the **Portal** dropdown menu, select your Dev Portal. diff --git a/app/catalog/apis.md b/app/catalog/apis.md index eb4b0ef7a8d..68678d28314 100644 --- a/app/catalog/apis.md +++ b/app/catalog/apis.md @@ -75,7 +75,10 @@ Additionally, you can link your API to a Gateway Service to allow developers to To create an API, do one of the following: {% navtabs "create-api" %} {% navtab "{{site.konnect_short_name}} UI" %} -Navigate to **Catalog > APIs** in the sidebar, and then click [**New API**](https://cloud.konghq.com/apis/create). +Navigate to **Catalog** in the sidebar, click the **APIs** tab, and then click [**New API**](https://cloud.konghq.com/apis/create). + +{:.info} +> If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **APIs** in the sidebar instead. {% endnavtab %} {% navtab "{{site.konnect_short_name}} API" %} Send a POST request to the [`/apis` endpoint](/api/konnect/api-builder/v3/#/operations/create-api): @@ -131,11 +134,17 @@ To version an API, do one of the following: {% navtabs "api-version" %} {% navtab "{{site.konnect_short_name}} UI" %} 1. In the {{site.konnect_short_name}} sidebar, click [**{{site.konnect_catalog}}**](https://cloud.konghq.com/service-catalog/). + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **Catalog > APIs** in the sidebar instead. 1. Click [**New API**](https://cloud.konghq.com/apis/create). 1. Enter a version in the **API version** field, or upload an API specification, which will set the version to match the API spec version. You can also add versions to existing APIs when you edit them if they aren't associated with an API specification. To manage multiple versions of the API specification, do the following: 1. In the {{site.konnect_short_name}} sidebar, click [**{{site.konnect_catalog}}**](https://cloud.konghq.com/service-catalog/). + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **Catalog > APIs** in the sidebar instead. 1. Click your API. 1. Click the **API specification** tab. 1. From the Actions dropdown menu, select "Add or update API spec". @@ -196,7 +205,10 @@ While you are creating or editing an API document, you can also choose to publis To create a new API document, do one of the following: {% navtabs "link-service" %} {% navtab "{{site.konnect_short_name}} UI" %} -1. Navigate to [**Catalog > APIs**](https://cloud.konghq.com/apis) in the sidebar and click your API. +1. Navigate to [**Catalog**](https://cloud.konghq.com/apis) in the sidebar and click your API. + + {:.info} + > If you're using {{site.konnect_catalog}} Classic, click ****Catalog > APIs**** in the sidebar instead. 1. Click the **Documentation** tab, and then click **New document** to create a new Markdown document. If you want to upload an existing Markdown documentation file, use the API or Terraform. @@ -261,7 +273,10 @@ The image must be a PNG, JPG, or SVG image under 500 KB that’s no larger than To upload an API image, do the following: 1. In the {{site.konnect_short_name}} sidebar, click **{{site.konnect_catalog}}**. -1. In the {{site.konnect_catalog}} sidebar, click **[APIs](https://cloud.konghq.com/apis)**. +1. Click the **[APIs](https://cloud.konghq.com/apis)** tab. + + {:.info} + > If you're using [{{site.konnect_catalog}} Classic](/catalog-classic/), click **APIs** in the sidebar instead. 1. Click the API you want to add the image to. 1. From the action menu, select "Edit". 1. Click **Upload image** and upload an image. @@ -449,7 +464,10 @@ rows: To publish your API, do one of the following: {% navtabs "link-service" %} {% navtab "{{site.konnect_short_name}} UI" %} -Navigate to [**Catalog > APIs**](https://cloud.konghq.com/apis) and click your API. Click the **Portals** tab, and then click **Publish API**. +Navigate to **Catalog**, click the **APIs** tab, and then click your API. Click the **Portals** tab, and then click **Publish API**. + +{:.info} +> If you're using [{{site.konnect_catalog}} Classic](/catalog-classic), click **APIs** in the sidebar instead. {% endnavtab %} {% navtab "{{site.konnect_short_name}} API" %} Send a PUT request to the [`/apis/{apiId}/publications/{portalId}` endpoint](/api/konnect/api-builder/v3/#/operations/publish-api-to-portal): diff --git a/app/catalog/integrations/api-gateway.md b/app/catalog/integrations/api-gateway.md index 3b44f28abc7..8bfb8880267 100644 --- a/app/catalog/integrations/api-gateway.md +++ b/app/catalog/integrations/api-gateway.md @@ -11,29 +11,31 @@ tags: - integrations breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog - gateway manager integration works_on: - konnect -description: The API Gateway integration is built directly into {{site.konnect_catalog}}, so no additional authorization is needed. +description: The API Gateway integration is built directly into {{site.konnect_catalog}} Classic, so no additional authorization is needed. related_resources: - text: Map API Gateway Services in {{site.konnect_catalog}} url: /how-to/map-api-gateway-resources/ - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ discovery_support: true bindable_entities: "Gateway Service" --- -This integration allows you to associate your {{site.konnect_catalog}} service to one or more Gateway Services registered in {{site.konnect_short_name}}’s API Gateway application. +{% include_cached catalog/catalog-classic-banner.md %} + +This integration allows you to associate your {{site.konnect_catalog}} Classic service to one or more Gateway Services registered in {{site.konnect_short_name}}’s API Gateway application. ## Authorize the API Gateway integration -The API Gateway integration is built directly into {{site.konnect_catalog}}. No additional authorization is required. As new Gateway Services are created in API Gateway, they are automatically discovered by {{site.konnect_catalog}} and surfaced as Resources. +The API Gateway integration is built directly into {{site.konnect_catalog}} Classic. No additional authorization is required. As new Gateway Services are created in API Gateway, they are automatically discovered by {{site.konnect_catalog}} Classic and surfaced as Resources. ## Resources diff --git a/app/catalog/integrations/aws-api-gateway.md b/app/catalog/integrations/aws-api-gateway.md index 53c70abef72..004108fdb9f 100644 --- a/app/catalog/integrations/aws-api-gateway.md +++ b/app/catalog/integrations/aws-api-gateway.md @@ -12,17 +12,17 @@ tags: - aws breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog works_on: - konnect -description: The AWS API Gateway integration allows you to associate your {{site.konnect_catalog}} service with one or more AWS API Gateway APIs. +description: The AWS API Gateway integration allows you to associate your {{site.konnect_catalog}} Classic service with one or more AWS API Gateway APIs. related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Import and map AWS API Gateway resources in {{site.konnect_catalog}} url: /how-to/install-and-map-aws-gateway-apis/ - text: "Discover AWS Gateway APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" @@ -35,27 +35,29 @@ discovery_support: true bindable_entities: "APIs" --- -The AWS API Gateway integration allows you to associate your {{site.konnect_catalog}} service with one or more AWS API Gateway APIs. +{% include_cached catalog/catalog-classic-banner.md %} + +The AWS API Gateway integration allows you to associate your {{site.konnect_catalog}} Classic service with one or more AWS API Gateway APIs. {% include /catalog/multi-resource.md %} For complete tutorials, see the following: -* [Discover and govern APIs with {{site.konnect_catalog}}](/how-to/discover-and-govern-apis-with-service-catalog/) -* [Discover AWS Gateway APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} API](/how-to/discover-aws-gateway-apis-using-konnect-api/) -* [Discover AWS Gateway APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI](/how-to/discover-aws-gateway-apis-using-konnect-ui/) +* [Discover and govern APIs with {{site.konnect_catalog}} Classic](/how-to/discover-and-govern-apis-with-service-catalog/) +* [Discover AWS Gateway APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API](/how-to/discover-aws-gateway-apis-using-konnect-api/) +* [Discover AWS Gateway APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI](/how-to/discover-aws-gateway-apis-using-konnect-ui/) -## Configure an IAM role in AWS for {{site.konnect_catalog}} +## Configure an IAM role in AWS for {{site.konnect_catalog}} Classic {% include /prereqs/service-catalog-iam.md %} ## Authorize the AWS API Gateway integration 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. +1. In the {{site.konnect_catalog}} sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. 1. Click **AWS API Gateway**. 1. Click **Add AWS API Gateway instance**. 1. From the **AWS region** dropdown, select your AWS region. -1. In the **IAM role ARN** field, enter the [IAM role you configured for {{site.konnect_catalog}}](#configure-an-iam-role-in-aws-for-service-catalog). +1. In the **IAM role ARN** field, enter the [IAM role you configured for {{site.konnect_catalog}} Classic](#configure-an-iam-role-in-aws-for-service-catalog). 1. In the **Display name** field, enter a name for your AWS API Gateway instance. 1. In the **Instance name** field, enter a unique identifier for your AWS API Gateway instance. 1. Click **Save**. @@ -73,7 +75,7 @@ columns: key: description rows: - entity: API - description: An AWS API Gateway API that relates to the {{site.konnect_catalog}} service. + description: An AWS API Gateway API that relates to the {{site.konnect_catalog}} Classic service. {% endtable %} diff --git a/app/catalog/integrations/azure-api-management.md b/app/catalog/integrations/azure-api-management.md index 62e3c011eb7..70c8360eaab 100644 --- a/app/catalog/integrations/azure-api-management.md +++ b/app/catalog/integrations/azure-api-management.md @@ -12,7 +12,7 @@ tags: - azure breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog @@ -21,19 +21,21 @@ works_on: description: placeholder related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ discovery_support: true bindable_entities: "APIs" --- -The Azure API Management integration allows you to associate your {{site.konnect_catalog}} service with one or more Azure API Management APIs. +{% include_cached catalog/catalog-classic-banner.md %} + +The Azure API Management integration allows you to associate your {{site.konnect_catalog}} Classic service with one or more Azure API Management APIs. {% include /catalog/multi-resource.md %} For complete tutorials, see the following: -* [Discover Azure API Management APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} API](/how-to/discover-azure-apis-with-konnect-api/) -* [Discover Azure API Management APIs in {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI](/how-to/discover-azure-apis-with-konnect-ui/) +* [Discover Azure API Management APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API](/how-to/discover-azure-apis-with-konnect-api/) +* [Discover Azure API Management APIs in {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI](/how-to/discover-azure-apis-with-konnect-ui/) ## Prerequisites @@ -48,7 +50,7 @@ Before you configure the Azure API Management integration, ensure the following: > **Note:** The Azure API Management integration uses OAuth for authentication and can only be configured through the {{site.konnect_short_name}} UI. 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. +1. In the {{site.konnect_catalog}} sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. 1. Click **Azure API Management**. 1. Click **Add Azure API Management instance**. 1. In the **Subscription ID** field, enter your Azure API subscription ID. @@ -72,7 +74,7 @@ columns: key: description rows: - entity: API - description: An Azure API Management API that relates to the {{site.konnect_catalog}} service. Only HTTP specs can be added via the the **API Specs** tab on a service. gRPC, WebSocket, and GraphQL specifications aren't supported. + description: An Azure API Management API that relates to the {{site.konnect_catalog}} Classic service. Only HTTP specs can be added via the the **API Specs** tab on a service. gRPC, WebSocket, and GraphQL specifications aren't supported. {% endtable %} diff --git a/app/catalog/integrations/azure-devops.md b/app/catalog/integrations/azure-devops.md index 295c9710327..ce775d5061d 100644 --- a/app/catalog/integrations/azure-devops.md +++ b/app/catalog/integrations/azure-devops.md @@ -14,7 +14,7 @@ tags: search_aliases: - service catalog breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ discovery_support: true @@ -22,23 +22,25 @@ bindable_entities: "Repositories" works_on: - konnect -description: "description: Provides information about the Azure DevOps integration, which lets the Konnect {{site.konnect_catalog}} read repository metadata from Azure DevOps and use it for service mapping and governance workflows." +description: "description: Provides information about the Azure DevOps integration, which lets the Konnect {{site.konnect_catalog}} Classic read repository metadata from Azure DevOps and use it for service mapping and governance workflows." related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ - - text: "Connect Azure DevOps repositories to Catalog with the Konnect API" + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ + - text: "Connect Azure DevOps repositories to {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API" url: /how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api/ - - text: "Connect Azure DevOps repositories to Catalog with the Konnect UI" + - text: "Connect Azure DevOps repositories to {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI" url: /how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui/ --- -The Azure DevOps integration lets Konnect {{site.konnect_catalog}} securely read and ingest repository metadata from Azure DevOps using a PAT with `Code:Read` access. Teams can reference and manage their source-code assets inside {{site.konnect_catalog}} and prepare for future governance and scorecard workflows. +{% include_cached catalog/catalog-classic-banner.md %} + +The Azure DevOps integration lets Konnect {{site.konnect_catalog}} Classic securely read and ingest repository metadata from Azure DevOps using a PAT with `Code:Read` access. Teams can reference and manage their source-code assets inside {{site.konnect_catalog}} Classic and prepare for future governance and scorecard workflows. For a complete tutorial, choose one of the following: -- [Connect Azure DevOps repositories to Catalog with the Konnect API](/how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api/) -- [Connect Azure DevOps repositories to Catalog with the Konnect UI](/how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui/) +- [Connect Azure DevOps repositories to {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API](/how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-api/) +- [Connect Azure DevOps repositories to {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI](/how-to/connect-azure-devops-to-the-konnect-catalog-with-the-konnect-ui/) ### Prerequisites You need to configure the following: @@ -63,7 +65,7 @@ You need to configure the following: {% endnavtab %} {% navtab "API" %} -Before you can discover Azure DevOps repositories in {{site.konnect_catalog}}, export your Azure organization name exactly as it appears in Azure DevOps: +Before you can discover Azure DevOps repositories in {{site.konnect_catalog}} Classic, export your Azure organization name exactly as it appears in Azure DevOps: ```sh export AZURE_DEVOPS_ORG_NAME="YOUR-ORG-NAME" diff --git a/app/catalog/integrations/datadog.md b/app/catalog/integrations/datadog.md index 017e9592789..765baebf5c9 100644 --- a/app/catalog/integrations/datadog.md +++ b/app/catalog/integrations/datadog.md @@ -14,26 +14,28 @@ tags: search_aliases: - service catalog breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: - konnect -description: The Datadog integration lets you connect Datadog entities directly to your {{site.konnect_catalog}} services. +description: The Datadog integration lets you connect Datadog entities directly to your {{site.konnect_catalog}} Classic services. discovery_support: true bindable_entities: "Datadog Monitor, Datadog Dashboard" related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Import and map Datadog resources in {{site.konnect_catalog}} url: /how-to/install-and-map-datadog-resources/ --- -The Datadog integration lets you connect Datadog entities directly to your {{site.konnect_catalog}} services. +{% include_cached catalog/catalog-classic-banner.md %} + +The Datadog integration lets you connect Datadog entities directly to your {{site.konnect_catalog}} Classic services. {% include /catalog/multi-resource.md %} -For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map Datadog resources in {{site.konnect_catalog}}](/how-to/install-and-map-datadog-resources/). +For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map Datadog resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-datadog-resources/). ## Prerequisites diff --git a/app/catalog/integrations/dynatrace.md b/app/catalog/integrations/dynatrace.md index 2c4529fde73..e3c68a34477 100644 --- a/app/catalog/integrations/dynatrace.md +++ b/app/catalog/integrations/dynatrace.md @@ -14,18 +14,18 @@ tags: search_aliases: - service catalog breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: - konnect -description: The Dynatrace integration lets you connect Dynatrace classic service-level objects directly to your {{site.konnect_catalog}} services. +description: The Dynatrace integration lets you connect Dynatrace classic service-level objects directly to your {{site.konnect_catalog}} Classic services. discovery_support: true bindable_entities: "Classic service-level object" related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "Monitor Dynatrace SLOs {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI" url: /how-to/monitor-dynatrace-slos-with-konnect-ui/ - text: "Monitor Dynatrace SLOs {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" @@ -34,12 +34,14 @@ related_resources: url: /how-to/set-up-dynatrace-with-otel/ --- -The Dynatrace integration lets you connect Dynatrace classic service-level objects directly to your {{site.konnect_catalog}} services. +{% include_cached catalog/catalog-classic-banner.md %} + +The Dynatrace integration lets you connect Dynatrace classic service-level objects directly to your {{site.konnect_catalog}} Classic services. {% include /catalog/multi-resource.md %} For a complete tutorial, see the following: -* [Monitor Dynatrace SLOs {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI](/how-to/monitor-dynatrace-slos-with-konnect-ui/) -* [Monitor Dynatrace SLOs {{site.konnect_catalog}} with the {{site.konnect_short_name}} API](/how-to/monitor-dynatrace-slos-with-konnect-api/) +* [Monitor Dynatrace SLOs {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI](/how-to/monitor-dynatrace-slos-with-konnect-ui/) +* [Monitor Dynatrace SLOs {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API](/how-to/monitor-dynatrace-slos-with-konnect-api/) ## Prerequisites @@ -56,7 +58,7 @@ You need to configure the following in Dynatrace SaaS: {% navtabs "dynatrace-integration" %} {% navtab "UI" %} 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. +1. In the {{site.konnect_catalog}} sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. 1. Click **Dynatrace**. 1. Click **Add Dynatrace instance**. 1. In the **Dynatrace API Base URL** field, enter your Dynatrace URL without the trailing `/`. For example: `https://whr42363.apps.dynatrace.com` diff --git a/app/catalog/integrations/github.md b/app/catalog/integrations/github.md index b064aa2001c..deca149c360 100644 --- a/app/catalog/integrations/github.md +++ b/app/catalog/integrations/github.md @@ -12,29 +12,31 @@ tags: - github breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: - konnect -description: The GitHub integration allows you to associate your {{site.konnect_catalog}} service to one or more GitHub repositories. +description: The GitHub integration allows you to associate your {{site.konnect_catalog}} Classic service to one or more GitHub repositories. search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Import and map GitHub resources in {{site.konnect_catalog}} url: /how-to/install-and-map-github-resources/ discovery_support: true bindable_entities: "Repositories" --- -The GitHub integration allows you to associate your {{site.konnect_catalog}} service to one or more GitHub repositories. +{% include_cached catalog/catalog-classic-banner.md %} + +The GitHub integration allows you to associate your {{site.konnect_catalog}} Classic service to one or more GitHub repositories. For each linked repository, the UI can show a **Repository Summary** with simple data pulled from the GitHub API, such as the number of open issues, open pull requests, most recently closed pull requests, languages, and more. {% include /catalog/multi-resource.md %} -For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map GitHub resources in {{site.konnect_catalog}}](/how-to/install-and-map-github-resources/). +For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map GitHub resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-github-resources/). ## Authorize the GitHub integration @@ -59,7 +61,7 @@ columns: key: description rows: - entity: Repository - description: A GitHub repository relating to the {{site.konnect_catalog}} service. + description: A GitHub repository relating to the {{site.konnect_catalog}} Classic service. {% endtable %} diff --git a/app/catalog/integrations/gitlab.md b/app/catalog/integrations/gitlab.md index 8ebfd531144..f08f01638be 100644 --- a/app/catalog/integrations/gitlab.md +++ b/app/catalog/integrations/gitlab.md @@ -11,18 +11,18 @@ tags: - gitlab breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: - konnect -description: The GitLab integration allows you to associate your {{site.konnect_catalog}} Service to one or more GitLab projects +description: The GitLab integration allows you to associate your {{site.konnect_catalog}} Classic Service to one or more GitLab projects search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Import and map self-managed GitLab resources in {{site.konnect_catalog}} @@ -32,14 +32,17 @@ related_resources: discovery_support: true bindable_entities: "Projects" --- -The GitLab integration allows you to associate your {{site.konnect_catalog}} service to one or more [GitLab projects](https://docs.gitlab.com/ee/user/get_started/get_started_projects.html). + +{% include_cached catalog/catalog-classic-banner.md %} + +The GitLab integration allows you to associate your {{site.konnect_catalog}} Classic service to one or more [GitLab projects](https://docs.gitlab.com/ee/user/get_started/get_started_projects.html). {% include /catalog/multi-resource.md %} For each linked project, the UI can show a **Project Summary** with simple data pulled from the GitLab API, such as the number of open issues, open merge requests, contributors, languages, and latest releases. For a complete tutorial using the {{site.konnect_short_name}} API, see the following: -* [Import and map self-managed GitLab resources in {{site.konnect_catalog}}](/how-to/install-and-map-gitlab-resources/) -* [Import and map SaaS GitLab resources in {{site.konnect_catalog}}](/how-to/install-and-map-gitlab-saas-resources/) +* [Import and map self-managed GitLab resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-gitlab-resources/) +* [Import and map SaaS GitLab resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-gitlab-saas-resources/) ## Prerequisites @@ -82,7 +85,7 @@ columns: key: description rows: - entity: Projects - description: "Organizes all the data for a specific development project that relates to a {{site.konnect_catalog}} service." + description: "Organizes all the data for a specific development project that relates to a {{site.konnect_catalog}} Classic service." {% endtable %} diff --git a/app/catalog/integrations/konnect-analytics.md b/app/catalog/integrations/konnect-analytics.md index d0c755f4f40..3a8cfef6b52 100644 --- a/app/catalog/integrations/konnect-analytics.md +++ b/app/catalog/integrations/konnect-analytics.md @@ -11,7 +11,7 @@ tags: - integrations breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: @@ -23,18 +23,20 @@ search_aliases: related_resources: - text: "Map {{site.observability}} reports in {{site.konnect_catalog}}" url: /how-to/map-analytics-resources/ - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ discovery_support: true discovery_default: true bindable_entities: "Report" --- +{% include_cached catalog/catalog-classic-banner.md %} + The {{site.observability}} integration will allow users to connect Reports from the {{site.observability}} product directly to their services. Users browsing the catalog will be able to see what reports are important to that service, and be brought directly to the report by clicking through. ## Authorize the {{site.observability}} integration -The {{site.observability}} integration is built directly into {{site.konnect_catalog}}. No additional authorization is required. +The {{site.observability}} integration is built directly into {{site.konnect_catalog}} Classic. No additional authorization is required. ## Resources diff --git a/app/catalog/integrations/pagerduty.md b/app/catalog/integrations/pagerduty.md index 27e3dcba13c..6c7ffedeffd 100644 --- a/app/catalog/integrations/pagerduty.md +++ b/app/catalog/integrations/pagerduty.md @@ -12,7 +12,7 @@ tags: - pagerduty breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog @@ -20,20 +20,22 @@ works_on: - konnect description: The PagerDuty integration allows you to provide a way to alert on information about current open incidents to consumers of the service directory. related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Import and map PagerDuty resources in {{site.konnect_catalog}} url: /how-to/install-and-map-pagerduty-resources/ discovery_support: true bindable_entities: "PagerDuty Service" --- +{% include_cached catalog/catalog-classic-banner.md %} + The PagerDuty integration allows you to provide a way to alert the service team (via PagerDuty services), as well as provide information on current open incidents to consumers of the service directory. {% include /catalog/multi-resource.md %} -For each linked PagerDuty service, a summary will be provided on the {{site.konnect_catalog}} service's details page, showing current unresolved incidents and the current on-call user. +For each linked PagerDuty service, a summary will be provided on the {{site.konnect_catalog}} Classic service's details page, showing current unresolved incidents and the current on-call user. -For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map PagerDuty resources in {{site.konnect_catalog}}](/how-to/install-and-map-pagerduty-resources/). +For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map PagerDuty resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-pagerduty-resources/). ## Authenticate the PagerDuty integration diff --git a/app/catalog/integrations/service-mesh.md b/app/catalog/integrations/service-mesh.md index 4c389afff11..1763d8c7e86 100644 --- a/app/catalog/integrations/service-mesh.md +++ b/app/catalog/integrations/service-mesh.md @@ -11,7 +11,7 @@ tags: - integrations breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: @@ -22,18 +22,20 @@ search_aliases: related_resources: - text: Map Service Mesh services in {{site.konnect_catalog}} url: /how-to/map-service-mesh-resources/ - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ discovery_support: true discovery_default: true bindable_entities: "Mesh Service" --- +{% include_cached catalog/catalog-classic-banner.md %} + The {{site.konnect_short_name}} Mesh integration allows users gain visibility into how their service is deployed across meshes and zones, determine whether their deployment is healthy, and (if used in conjunction with other built-in integrations) to identify links between their mesh services and other {{site.konnect_short_name}} resources. ## Authorize the Service Mesh integration -The Service Mesh integration is built directly into {{site.konnect_catalog}}. No additional authorization is required. As new Mesh Services are created, they are automatically discovered by {{site.konnect_catalog}} and surfaced as Resources. +The Service Mesh integration is built directly into {{site.konnect_catalog}} Classic. No additional authorization is required. As new Mesh Services are created, they are automatically discovered by {{site.konnect_catalog}} Classic and surfaced as Resources. ## Resources diff --git a/app/catalog/integrations/slack.md b/app/catalog/integrations/slack.md index ccbdbb86030..ea545dd62f1 100644 --- a/app/catalog/integrations/slack.md +++ b/app/catalog/integrations/slack.md @@ -12,17 +12,17 @@ tags: - slack breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog works_on: - konnect -description: The Slack integration allows you to see Slack communication channels that are relevant to a {{site.konnect_catalog}} service. +description: The Slack integration allows you to see Slack communication channels that are relevant to a {{site.konnect_catalog}} Classic service. related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Integrations url: /catalog/integrations/ - text: Import and map Slack resources in {{site.konnect_catalog}} @@ -33,11 +33,12 @@ bindable_entities: "Slack Channel" mechanism: "pull/ingestion model" --- +{% include_cached catalog/catalog-classic-banner.md %} -The Slack integration allows you to see communication channels (via [Slack channels](https://slack.com/help/articles/360017938993-What-is-a-channel)) that are relevant to a {{site.konnect_catalog}} service. +The Slack integration allows you to see communication channels (via [Slack channels](https://slack.com/help/articles/360017938993-What-is-a-channel)) that are relevant to a {{site.konnect_catalog}} Classic service. {% include /catalog/multi-resource.md %} -For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map Slack resources in {{site.konnect_catalog}}](/how-to/install-and-map-slack-resources/). +For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map Slack resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-slack-resources/). ## Prerequisites @@ -64,7 +65,7 @@ columns: rows: - entity: Slack Channel description: - A Slack channel that indicates who owns the {{site.konnect_catalog}} service. Ideally, this helps users identify who they can contact if they have questions about a service. + A Slack channel that indicates who owns the {{site.konnect_catalog}} Classic service. Ideally, this helps users identify who they can contact if they have questions about a service. {% endtable %} diff --git a/app/catalog/integrations/sonarqube.md b/app/catalog/integrations/sonarqube.md index 044f651f8a4..9e7ce7ff059 100644 --- a/app/catalog/integrations/sonarqube.md +++ b/app/catalog/integrations/sonarqube.md @@ -14,30 +14,32 @@ tags: search_aliases: - service catalog breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ works_on: - konnect -description: The SonarQube integration lets you connect SonarQube SaaS projects directly to your {{site.konnect_catalog}} services. +description: The SonarQube integration lets you connect SonarQube SaaS projects directly to your {{site.konnect_catalog}} Classic services. discovery_support: true bindable_entities: "Projects" related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "Monitor SonarQube projects {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI" url: /how-to/monitor-sonarqube-projects-with-konnect-ui/ - text: "Monitor SonarQube projects {{site.konnect_catalog}} with the {{site.konnect_short_name}} API" url: /how-to/monitor-sonarqube-projects-with-konnect-api/ --- -The SonarQube integration lets you connect [SonarQube projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects) directly to your {{site.konnect_catalog}} services. +{% include_cached catalog/catalog-classic-banner.md %} + +The SonarQube integration lets you connect [SonarQube projects](https://docs.sonarsource.com/sonarqube-cloud/managing-your-projects) directly to your {{site.konnect_catalog}} Classic services. {% include /catalog/multi-resource.md %} For a complete tutorial, see the following: -* [Monitor SonarQube projects {{site.konnect_catalog}} with the {{site.konnect_short_name}} UI](/how-to/monitor-sonarqube-projects-with-konnect-ui/) -* [Monitor SonarQube projects {{site.konnect_catalog}} with the {{site.konnect_short_name}} API](/how-to/monitor-sonarqube-projects-with-konnect-api/) +* [Monitor SonarQube projects {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} UI](/how-to/monitor-sonarqube-projects-with-konnect-ui/) +* [Monitor SonarQube projects {{site.konnect_catalog}} Classic with the {{site.konnect_short_name}} API](/how-to/monitor-sonarqube-projects-with-konnect-api/) ## Prerequisites @@ -52,7 +54,7 @@ You need to configure the following in SonarQube SaaS: {% navtabs "sonarqube-integration" %} {% navtab "UI" %} 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. +1. In the {{site.konnect_catalog}} sidebar, click **[Integrations](https://cloud.konghq.com/us/service-catalog/integrations)**. 1. Click **SonarQube**. 1. Click **Add SonarQube instance**. 1. In the **SonarQube API key** field, enter your SonarQube personal access token. diff --git a/app/catalog/integrations/swaggerhub.md b/app/catalog/integrations/swaggerhub.md index d3636a6e83e..97085f637af 100644 --- a/app/catalog/integrations/swaggerhub.md +++ b/app/catalog/integrations/swaggerhub.md @@ -12,26 +12,28 @@ tags: - swaggerhub breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog works_on: - konnect -description: The SwaggerHub integration lets you connect SwaggerHub API specs directly to your {{site.konnect_catalog}} services. +description: The SwaggerHub integration lets you connect SwaggerHub API specs directly to your {{site.konnect_catalog}} Classic services. related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Import and map SwaggerHub resources in {{site.konnect_catalog}} url: /how-to/install-and-map-swaggerhub-resources/ discovery_support: true bindable_entities: "SwaggerHub API version" --- -The SwaggerHub integration lets you connect SwaggerHub API specs directly to your {{site.konnect_catalog}} services. +{% include_cached catalog/catalog-classic-banner.md %} + +The SwaggerHub integration lets you connect SwaggerHub API specs directly to your {{site.konnect_catalog}} Classic services. {% include /catalog/multi-resource.md %} -For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map SwaggerHub resources in {{site.konnect_catalog}}](/how-to/install-and-map-swaggerhub-resources/). +For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map SwaggerHub resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-swaggerhub-resources/). ## Prerequisites diff --git a/app/catalog/integrations/traceable.md b/app/catalog/integrations/traceable.md index fe2144ebc55..3074320048c 100644 --- a/app/catalog/integrations/traceable.md +++ b/app/catalog/integrations/traceable.md @@ -12,17 +12,17 @@ tags: - traceable breadcrumbs: - - /catalog/ + - /catalog-classic/ - /catalog/integrations/ search_aliases: - service catalog works_on: - konnect -description: The Traceable integration lets you connect Traceable entities directly to your {{site.konnect_catalog}} services. +description: The Traceable integration lets you connect Traceable entities directly to your {{site.konnect_catalog}} Classic services. related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Traceable plugin url: /plugins/traceable/ - text: Import and map Traceable resources in {{site.konnect_catalog}} @@ -31,10 +31,12 @@ discovery_support: true bindable_entities: "Traceable Service" --- -The Traceable integration lets you connect Traceable Services directly to your {{site.konnect_catalog}} services. +{% include_cached catalog/catalog-classic-banner.md %} + +The Traceable integration lets you connect Traceable Services directly to your {{site.konnect_catalog}} Classic services. {% include /catalog/multi-resource.md %} -For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map Traceable resources in {{site.konnect_catalog}}](/how-to/install-and-map-traceable-resources/). +For a complete tutorial using the {{site.konnect_short_name}} API, see [Import and map Traceable resources in {{site.konnect_catalog}} Classic](/how-to/install-and-map-traceable-resources/). ## Authenticate the Traceable integration diff --git a/app/catalog/mcp-registry.md b/app/catalog/mcp-registry.md index beb26997eb4..f064037da7c 100644 --- a/app/catalog/mcp-registry.md +++ b/app/catalog/mcp-registry.md @@ -1,5 +1,5 @@ --- -title: "MCP Registries in {{site.konnect_catalog}}" +title: "MCP Registries in {{site.konnect_catalog}} Classic" content_type: reference layout: reference tech_preview: true @@ -8,16 +8,16 @@ products: works_on: - konnect -description: An MCP Registry is a centralized publishing and discovery endpoint for MCP servers within your organization. Learn how to register your MCP servers in {{site.konnect_short_name}} {{site.konnect_catalog}}. +description: An MCP Registry is a centralized publishing and discovery endpoint for MCP servers within your organization. Learn how to register your MCP servers in {{site.konnect_short_name}} {{site.konnect_catalog}} Classic. breadcrumbs: - - /catalog/ + - /catalog-classic/ search_aliases: - service catalog - mcp related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "MCP traffic gateway" url: /mcp/ - text: "MCP clients in Insomnia" @@ -25,13 +25,15 @@ related_resources: faqs: - q: Is the MCP Registry feature GA? a: | - No, MCP Registries in Catalog is only available in Tech Preview via {{site.konnect_short_name}} Labs. + No, MCP Registries in {{site.konnect_catalog}} Classic is only available in Tech Preview via {{site.konnect_short_name}} Labs. This feature is built on top of Anthropic’s MCP Registry API specification, which is still rapidly evolving. Because the underlying standard continues to change, we cannot responsibly commit to GA timelines or long-term stability guarantees at this time. We are actively iterating in partnership with customers who are exploring MCP-based agent architectures and will evaluate GA readiness as the specification matures. --- +{% include_cached catalog/catalog-classic-banner.md %} + ## What is an MCP Registry? An MCP Registry is a centralized publishing and discovery endpoint for MCP servers within your organization. @@ -42,14 +44,14 @@ As organizations experiment with AI agents, MCP servers are often embedded direc * Which agents should use which servers * How those servers should be governed -MCP Registries extend {{site.konnect_short_name}} {{site.konnect_catalog}} to provide a structured, standards-based way to register and manage MCP servers, helping Platform Teams maintain visibility and control as AI adoption scales. +MCP Registries extend {{site.konnect_short_name}} {{site.konnect_catalog}} Classic to provide a structured, standards-based way to register and manage MCP servers, helping Platform Teams maintain visibility and control as AI adoption scales. This feature is built on top of the MCP Registry API specification defined by {{ site.anthropic }}’s [open source project](https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/api/openapi.yaml). The specification allows flexibility in how registries are structured, so you can model them according to your organization’s governance needs. -## Enable MCP Registries in {{site.konnect_catalog}} +## Enable MCP Registries in {{site.konnect_catalog}} Classic -MCP Registries in {{site.konnect_catalog}} are currently available in tech preview via {{site.konnect_short_name}} Labs. +MCP Registries in {{site.konnect_catalog}} Classic are currently available in tech preview via {{site.konnect_short_name}} Labs. 1. In the {{site.konnect_short_name}} sidebar, navigate to **Organizations**. 1. In the Organization sidebar, click **Labs**. diff --git a/app/catalog/migrate-api-specs-to-apis.md b/app/catalog/migrate-api-specs-to-apis.md index 5d3a9f1098d..d62032c3181 100644 --- a/app/catalog/migrate-api-specs-to-apis.md +++ b/app/catalog/migrate-api-specs-to-apis.md @@ -15,8 +15,8 @@ breadcrumbs: search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Scorecards url: /catalog/scorecards/ - text: "{{site.konnect_catalog}} integrations" diff --git a/app/catalog/scorecards.md b/app/catalog/scorecards.md index 8bda6b11f4c..c2de702e0fb 100644 --- a/app/catalog/scorecards.md +++ b/app/catalog/scorecards.md @@ -8,22 +8,24 @@ products: works_on: - konnect -description: Scorecards in {{site.konnect_catalog}} allow platform teams to monitor services for compliance with Kong-recommended and industry-defined best practices in {{site.konnect_short_name}}. +description: Scorecards in {{site.konnect_catalog}} Classic allow platform teams to monitor services for compliance with Kong-recommended and industry-defined best practices in {{site.konnect_short_name}}. breadcrumbs: - - /catalog/ + - /catalog-classic/ search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: "{{site.konnect_catalog}} services" url: /catalog/services/ - text: Catalog integrations url: /catalog/integrations/ --- -A {{site.konnect_catalog}} scorecard helps you evaluate services based on validation criteria. Scorecards help you detect issues, like whether there are services in the catalog that don't have an on-call engineer assigned, or if you have GitHub repositories with stale pull requests that aren't getting reviewed or closed. +{% include_cached catalog/catalog-classic-banner.md %} + +A {{site.konnect_catalog}} Classic scorecard helps you evaluate services based on validation criteria. Scorecards help you detect issues, like whether there are services in the catalog that don't have an on-call engineer assigned, or if you have GitHub repositories with stale pull requests that aren't getting reviewed or closed. From the scorecard view, you can view details on either a per-service or per-criteria basis. @@ -31,7 +33,7 @@ You can use a prebuilt scorecard template that includes criteria from Kong and i ## Scorecard templates -{{site.konnect_short_name}} provides several scorecard templates to help ensure your {{site.konnect_catalog}} services adhere to industry best practices. +{{site.konnect_short_name}} provides several scorecard templates to help ensure your {{site.konnect_catalog}} Classic services adhere to industry best practices. {% table %} @@ -59,7 +61,7 @@ To enable a scorecard on a service: {% navtabs "scorecards" %} {% navtab "UI" %} 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **[Scorecards](https://cloud.konghq.com/service-catalog/scorecards)**. +1. In the {{site.konnect_catalog}} sidebar, click **[Scorecards](https://cloud.konghq.com/service-catalog/scorecards)**. 1. Click **New Scorecard**. 1. From the **Scorecard template** dropdown menu, select your template or select custom scorecard. 1. (Optional) If you want to add an additional section or criteria, click **Add criteria** or **Add section**. diff --git a/app/catalog/services.md b/app/catalog/services.md index 0572bec7440..f8ef7d4dde9 100644 --- a/app/catalog/services.md +++ b/app/catalog/services.md @@ -1,5 +1,5 @@ --- -title: "{{site.konnect_catalog}} services" +title: "{{site.konnect_catalog}} Classic services" content_type: reference layout: reference @@ -8,15 +8,15 @@ products: works_on: - konnect -description: Learn about services in {{site.konnect_catalog}} and how to configure them. +description: Learn about services in {{site.konnect_catalog}} Classic and how to configure them. breadcrumbs: - - /catalog/ + - /catalog-classic/ search_aliases: - service catalog related_resources: - - text: "{{site.konnect_catalog}}" - url: /catalog/ + - text: "{{site.konnect_catalog}} Classic" + url: /catalog-classic/ - text: Scorecards url: /catalog/scorecards/ - text: Traceable integration @@ -32,33 +32,35 @@ related_resources: - text: PagerDuty integration url: /catalog/integrations/pagerduty/ faqs: - - q: What's the difference between a Gateway Service and a {{site.konnect_catalog}} service? + - q: What's the difference between a Gateway Service and a {{site.konnect_catalog}} Classic service? a: | - A [Gateway Service](/gateway/entities/service/) is a {{site.base_gateway}} entity that represents an upstream service in your system and is the business logic component that's responsible for responding to requests. A {{site.konnect_catalog}} service is a collection of one or more resources from {{site.konnect_catalog}} integrations. + A [Gateway Service](/gateway/entities/service/) is a {{site.base_gateway}} entity that represents an upstream service in your system and is the business logic component that's responsible for responding to requests. A {{site.konnect_catalog}} Classic service is a collection of one or more resources from {{site.konnect_catalog}} Classic integrations. --- -A {{site.konnect_catalog}} service is a collection of one or more resources from integrations. +{% include_cached catalog/catalog-classic-banner.md %} -A {{site.konnect_catalog}} service represents the following: +A {{site.konnect_catalog}} Classic service is a collection of one or more resources from integrations. + +A {{site.konnect_catalog}} Classic service represents the following: * A unit of software that is typically owned by a single team * Exposes one or more APIs -* May be dependent on other {{site.konnect_catalog}} services (as either upstream or downstream) +* May be dependent on other {{site.konnect_catalog}} Classic services (as either upstream or downstream) -{{site.konnect_catalog}} services allow you to gain visibility into all resources in your organization, including what teams or people own them. +{{site.konnect_catalog}} Classic services allow you to gain visibility into all resources in your organization, including what teams or people own them. -To create a {{site.konnect_catalog}} service, do one of the following: +To create a {{site.konnect_catalog}} Classic service, do one of the following: {% navtabs "service" %} {% navtab "UI" %} 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **Services**. +1. In the {{site.konnect_catalog}} sidebar, click **Services**. 1. Click **New service** and configure the details about your service. 1. Map the service to an integration: 1. Click the service. 1. Select "Map resources" from the **Action** dropdown menu. {% endnavtab %} {% navtab "API" %} -1. Create a {{site.konnect_catalog}} service by sending a POST request to the [`/catalog-services` endpoint](/api/konnect/service-catalog/v1/#/operations/create-catalog-service): +1. Create a {{site.konnect_catalog}} Classic service by sending a POST request to the [`/catalog-services` endpoint](/api/konnect/service-catalog/v1/#/operations/create-catalog-service): {% capture service %} {% konnect_api_request %} @@ -128,13 +130,13 @@ resource "konnect_catalog_service" "my_catalogservice" { {% endnavtab %} {% endnavtabs %} -## Map APIs to a service in {{site.konnect_catalog}} +## Map APIs to a service in {{site.konnect_catalog}} Classic -APIs can be associated with {{site.konnect_catalog}} services, which allows API consumers and service owners to see which APIs and services are associated with each other. If you've already assigned API specs to a service from integrations, [migrate them to APIs](/catalog/migrate-api-specs-to-apis/). +APIs can be associated with {{site.konnect_catalog}} Classic services, which allows API consumers and service owners to see which APIs and services are associated with each other. If you've already assigned API specs to a service from integrations, [migrate them to APIs](/catalog/migrate-api-specs-to-apis/). {% include_cached /catalog/note-api-spec-snapshot.md %} -To link APIs with a {{site.konnect_catalog}} service, you need the following [{{site.konnect_short_name}} roles](/konnect-platform/teams-and-roles/#catalog) at a minimum for the services and APIs: +To link APIs with a {{site.konnect_catalog}} Classic service, you need the following [{{site.konnect_short_name}} roles](/konnect-platform/teams-and-roles/#catalog) at a minimum for the services and APIs: * API viewer * Service viewer * Service admin @@ -143,14 +145,14 @@ To link APIs to a service, do the following: {% navtabs "map-apis" %} {% navtab "UI" %} 1. In the {{site.konnect_short_name}} sidebar, click **Catalog**. -1. In the Catalog sidebar, click **Services**. +1. In the {{site.konnect_catalog}} sidebar, click **Services**. 1. Click a service you want to associate an API with. 1. Click the **APIs** tab. 1. Click **Link API**. 1. Select the APIs you want to link. 1. Click **Link APIs**. -You will now see the API with your API spec linked to the {{site.konnect_catalog}} service. Users who view APIs will also be able to see any linked {{site.konnect_catalog}} services. +You will now see the API with your API spec linked to the {{site.konnect_catalog}} Classic service. Users who view APIs will also be able to see any linked {{site.konnect_catalog}} Classic services. {% endnavtab %} {% navtab "API" %}