added the azure names of the supported resources + changed the supported resources capitalization

sivanel97 · sivanel97 · commit 943b9c8d267a · 2025-10-28T14:29:31.000+02:00
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/datadog/datadog.md b/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/datadog/datadog.md
@@ -26,7 +26,7 @@ This integration allows you to:
 - Map and organize your desired Datadog resources and their metadata in Port (see supported resources below).
 - Watch for Datadog object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 
-### Supported Resources
+### Supported resources
 
 - [`Monitor`](https://docs.datadoghq.com/api/latest/monitors/#get-all-monitor-details)
 - [`Service`](https://docs.datadoghq.com/api/latest/service-definition/#get-all-service-definitions)
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/dynatrace/dynatrace.md b/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/dynatrace/dynatrace.md
@@ -22,7 +22,7 @@ This integration allows you to:
 - Map and organize your desired Dynatrace resources and their metadata in Port (see supported resources below).
 - Watch for Dynatrace object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Dynatrace into Port are listed below. It is possible to reference any field that appears in the API responses linked below for the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/newrelic.md b/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/newrelic.md
@@ -23,7 +23,7 @@ This integration allows you to:
 - Map and organize your desired New Relic resources and their metadata in Port (see supported resources below).
 - Watch for New Relic object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from New Relic into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/sentry.md b/docs/build-your-software-catalog/sync-data-to-catalog/apm-alerting/sentry.md
@@ -27,7 +27,7 @@ This integration allows you to:
 - Map and organize your desired Sentry resources and their metadata in Port (see supported resources below).
 - Watch for Sentry object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Sentry into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/argocd/argocd.md b/docs/build-your-software-catalog/sync-data-to-catalog/argocd/argocd.md
@@ -25,7 +25,7 @@ This integration allows you to:
 - Map and organize your desired ArgoCD resources and their metadata in Port (see supported resources below).
 - Watch for ArgoCD object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from ArgoCD into Port are listed below.
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/cicd/jenkins/jenkins.md b/docs/build-your-software-catalog/sync-data-to-catalog/cicd/jenkins/jenkins.md
@@ -36,7 +36,7 @@ This integration allows you to:
 - Map and organize your desired Jenkins resources and their metadata in Port (see supported resources below).
 - Watch for Jenkins object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 - `job` - (`<your-jenkins-host>/api/json`)
 - `build` - (`<your-jenkins-host>/api/json`)
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/cicd/octopus-deploy/octopus-deploy.md b/docs/build-your-software-catalog/sync-data-to-catalog/cicd/octopus-deploy/octopus-deploy.md
@@ -25,7 +25,7 @@ This integration allows you to:
 - Map and organize your desired Octopus Deploy resources and their metadata in Port (see supported resources below).
 - Watch for Octopus Deploy object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 Some of the resources that can be ingested from Octopus Deploy into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/cloud-cost/kubecost/kubecost.md b/docs/build-your-software-catalog/sync-data-to-catalog/cloud-cost/kubecost/kubecost.md
@@ -26,7 +26,7 @@ This integration allows you to:
 - Watch for Kubecost object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Kubecost into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/cloud-cost/opencost.md b/docs/build-your-software-catalog/sync-data-to-catalog/cloud-cost/opencost.md
@@ -23,7 +23,7 @@ This integration allows you to:
 - Watch for Opencost object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Opencost into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/examples/mapping_extra_resources.md b/docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/aws/examples/mapping_extra_resources.md
@@ -43,7 +43,7 @@ The AWS Integration relies on AWS's Cloud Control API. That means:
    - **If so**: Great! It's supported.
    - **If not**: Please contact us or contribute by [adding support](https://ocean.getport.io/develop-an-integration/) to [the integration](https://github.com/port-labs/ocean/tree/main/integrations/aws) yourself.
 
-For the full list of supported resources, refer to [AWS Cloud Control API Supported Resources](https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/supported-resources.html).
+For the full list of supported resources, refer to [AWS Cloud Control API Supported resources](https://docs.aws.amazon.com/cloudcontrolapi/latest/userguide/supported-resources.html).
 
 ## Resources supported by Cloud Control API but not supported in AWS Integration
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/gcp/examples/mapping_extra_resources.md b/docs/build-your-software-catalog/sync-data-to-catalog/cloud-providers/gcp/examples/mapping_extra_resources.md
@@ -29,7 +29,7 @@ The GCP Integration is relying on GCP's Asset Inventory API. That means:
 
 ## Mapping the resource to Port
 
-After you've found the resource in the [Cloud Asset Supported Resources](https://cloud.google.com/asset-inventory/docs/supported-asset-types), you can map it to Port by following these steps:
+After you've found the resource in the [Cloud Asset Supported resources](https://cloud.google.com/asset-inventory/docs/supported-asset-types), you can map it to Port by following these steps:
 
 ### Blueprint
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/aikido/aikido.md b/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/aikido/aikido.md
@@ -20,7 +20,7 @@ This integration allows you to:
 - Map repositories and their security findings
 - Maintain real-time synchronization between Aikido and Port
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Aikido into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/armorcode/armorcode.md b/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/armorcode/armorcode.md
@@ -19,7 +19,7 @@ This integration allows you to:
 - Map products, sub-products, and their security findings.
 - Monitor security posture across your software catalog.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from ArmorCode into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/checkmarx/checkmarx.md b/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/checkmarx/checkmarx.md
@@ -13,7 +13,7 @@ import DockerParameters from "./_checkmarx_docker_parameters.mdx"
 This integration allows you to model Checkmarx One resources in your software catalog and ingest data into them.  
 It lets you map and organize the desired Checkmarx One resources and their metadata in Port (see supported resources below).
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Checkmarx One into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/snyk/snyk.md b/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/snyk/snyk.md
@@ -21,7 +21,7 @@ This integration allows you to:
 - Map and organize your desired Snyk resources and their metadata in Port (see supported resources below).
 - Watch for Snyk object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Snyk into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/sonarqube/sonarqube.md b/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/sonarqube/sonarqube.md
@@ -27,7 +27,7 @@ This integration allows you to:
 - Map and organize your desired SonarQube resources and their metadata in Port (see supported resources below).
 - Watch for SonarQube object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from SonarQube into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/wiz.md b/docs/build-your-software-catalog/sync-data-to-catalog/code-quality-security/wiz.md
@@ -26,7 +26,7 @@ This integration allows you to:
 - Watch for Wiz object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Wiz into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/feature-management/launchdarkly/launchdarkly.md b/docs/build-your-software-catalog/sync-data-to-catalog/feature-management/launchdarkly/launchdarkly.md
@@ -27,7 +27,7 @@ This integration allows you to:
 - Map and organize your desired LaunchDarkly resources and their metadata in Port (see supported resources below).
 - Watch for LaunchDarkly object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from LaunchDarkly into Port are listed below.  
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/_azuredevops_exporter_supported_resources.mdx b/docs/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/_azuredevops_exporter_supported_resources.mdx
@@ -5,7 +5,7 @@
 - [`pull-request`](https://learn.microsoft.com/en-us/rest/api/azure/devops/git/pull-requests/get-pull-requests?view=azure-devops-rest-7.1&tabs=HTTP#gitpullrequest)
 - [`pipeline`](https://learn.microsoft.com/en-us/rest/api/azure/devops/pipelines/pipelines/list?view=azure-devops-rest-7.2#pipeline)
 - [`build`](https://learn.microsoft.com/en-us/rest/api/azure/devops/build/builds/list?view=azure-devops-rest-7.1&tabs=HTTP#build)
-- [`pipeline-stage`](https://learn.microsoft.com/en-us/rest/api/azure/devops/build/timeline/get?view=azure-devops-rest-7.1)
+- [`pipeline-stage`](https://learn.microsoft.com/en-us/rest/api/azure/devops/build/timeline/get?view=azure-devops-rest-7.1) (`Build timeline`)
 - [`pipeline-run`](https://learn.microsoft.com/en-us/rest/api/azure/devops/pipelines/runs/list?view=azure-devops-rest-7.1&tabs=HTTP#run)
 - [`iteration`](https://learn.microsoft.com/en-us/rest/api/azure/devops/work/iterations/list?view=azure-devops-rest-7.1&tabs=HTTP#teamsettingsiteration)
 - [`user`](https://learn.microsoft.com/en-us/rest/api/azure/devops/memberentitlementmanagement/user-entitlements/list?view=azure-devops-rest-4.1&tabs=HTTP)
@@ -16,6 +16,6 @@
 - [`release`](https://learn.microsoft.com/en-us/rest/api/azure/devops/release/releases?view=azure-devops-rest-7.1)
 - [`environment`](https://learn.microsoft.com/en-us/rest/api/azure/devops/distributedtask/environments/list?view=azure-devops-rest-7.1&tabs=HTTP)
 - [`release-deployment`](https://learn.microsoft.com/en-us/rest/api/azure/devops/release/deployments/list?view=azure-devops-rest-7.1&tabs=HTTP)
-- [`pipeline-deployment`](https://learn.microsoft.com/en-us/rest/api/azure/devops/distributedtask/environmentdeployment-records/list?view=azure-devops-rest-7.1)
+- [`pipeline-deployment`](https://learn.microsoft.com/en-us/rest/api/azure/devops/distributedtask/environmentdeployment-records/list?view=azure-devops-rest-7.1) (`Environment deployment records`)
 - [`test-run`](https://learn.microsoft.com/en-us/rest/api/azure/devops/test/runs/list?view=azure-devops-rest-7.1&tabs=HTTP)
 - [`file`](https://learn.microsoft.com/en-us/rest/api/azure/devops/git/items/get-items-batch?view=azure-devops-rest-7.1&tabs=HTTP)
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/azure-devops.md b/docs/build-your-software-catalog/sync-data-to-catalog/git/azure-devops/azure-devops.md
@@ -16,7 +16,7 @@ This integration allows you to:
 - Manage Port entities using GitOps.
 
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Azure DevOps into Port are listed below.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/git/gitlab/gitlab.md b/docs/build-your-software-catalog/sync-data-to-catalog/git/gitlab/gitlab.md
@@ -22,7 +22,7 @@ This integration allows you to:
 - Watch for GitLab object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 - Manage Port entities using GitOps.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from GitLab into Port are listed below.  
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/firehydrant.md b/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/firehydrant.md
@@ -26,7 +26,7 @@ This integration allows you to:
 - Watch for FireHydrant object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from FireHydrant into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/opsgenie/opsgenie.md b/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/opsgenie/opsgenie.md
@@ -28,7 +28,7 @@ This integration allows you to:
 - Watch for Opsgenie object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Opsgenie into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/servicenow.md b/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/servicenow.md
@@ -29,7 +29,7 @@ This integration allows you to:
 
 - Map and organize your desired ServiceNow resources and their metadata in Port (see supported resources below).
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from ServiceNow into Port are listed below. 
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/statuspage/statuspage.md b/docs/build-your-software-catalog/sync-data-to-catalog/incident-management/statuspage/statuspage.md
@@ -26,7 +26,7 @@ This integration allows you to:
 - Map and organize your desired Statuspage resources and their metadata in Port (see supported resources below).
 - Watch for Statuspage object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Statuspage into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/komodor.md b/docs/build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/komodor.md
@@ -17,7 +17,7 @@ Port's Komodor integration allows you to model [Komodor](https://komodor.com/) r
 
 This integration allows you to map, organize, and sync your desired Komodor resources and their metadata in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Komodor into Port are listed below:
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/kubernetes/kubernetes.md b/docs/build-your-software-catalog/sync-data-to-catalog/kubernetes-stack/kubernetes/kubernetes.md
@@ -36,7 +36,7 @@ This integration allows you to:
 - Use relations to create a complete, easily digestible map of your K8s cluster inside Port;
 - Map your Kubernetes resources from common CRDs such as ArgoCD, Istio and more;
 
-### Supported Resources
+### Supported resources
 
 The default resources ingested by the integration are:
 - [`Namespaces`](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/other/amplication.md b/docs/build-your-software-catalog/sync-data-to-catalog/other/amplication.md
@@ -23,7 +23,7 @@ This integration allows you to:
 - Leverage code generation to accelerate development and maintain consistency.
 - Poll Amplication for templates, resources, and outdated version alerts to keep you in sync with your Amplication resources.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Amplication into Port are listed below:
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/other/backstage.md b/docs/build-your-software-catalog/sync-data-to-catalog/other/backstage.md
@@ -17,7 +17,7 @@ This integration allows you to:
 - Map and organize your desired Backstage resources and their metadata in Port (see supported resources below).
 - Watch for Backstage object changes (create/update/delete) in real-time, and automatically apply the changes to your entities in Port.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Backstage into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/project-management/jira-server/jira-server.md b/docs/build-your-software-catalog/sync-data-to-catalog/project-management/jira-server/jira-server.md
@@ -20,7 +20,7 @@ This integration allows you to:
 - Watch for Jira Server object changes (create/update/delete) via scheduled resync, and automatically apply the changes to your software catalog.
 - Define self-service actions that can create/delete Jira Server objects or perform any other logic on Jira Server resources.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Jira Server into Port are listed below.  
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/project-management/jira/jira.md b/docs/build-your-software-catalog/sync-data-to-catalog/project-management/jira/jira.md
@@ -34,7 +34,7 @@ This integration allows you to:
 - Watch for Jira object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 - Define self-service actions that can create/delete Jira objects or perform any other logic on Jira resources.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Jira into Port are listed below.  
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/project-management/linear/linear.md b/docs/build-your-software-catalog/sync-data-to-catalog/project-management/linear/linear.md
@@ -25,7 +25,7 @@ This integration allows you to:
 - Map and organize your desired Linear resources and their metadata in Port (see supported resources below).
 - Watch for Linear object changes (create/update/delete) in real-time, and automatically apply the changes to your software catalog.
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Linear into Port are listed below.  
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
diff --git a/docs/build-your-software-catalog/sync-data-to-catalog/terraform-cloud/terraform-cloud.md b/docs/build-your-software-catalog/sync-data-to-catalog/terraform-cloud/terraform-cloud.md
@@ -34,7 +34,7 @@ Port supports both Terraform Cloud and Terraform Enterprise versions (self hoste
 If installing Port exporter for Terraform Enterprise, you will be required to specify your Terraform 's host URL by passing the following parameter to the installer: `integration.config.appHost` 
 :::
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from Terraform Cloud into Port are listed below. It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
 
diff --git a/docs/generalTemplates/_integration_template.md b/docs/generalTemplates/_integration_template.md
@@ -23,7 +23,7 @@ If there are any special capabilities of the integration such as gitops, multi-a
 - Manage Port entities using GitOps.
 -->
 
-### Supported Resources
+### Supported resources
 
 The resources that can be ingested from X into Port are listed below.  
 It is possible to reference any field that appears in the API responses linked below in the mapping configuration.
