Merge branch 'main' into hybridrunnerdocupd

Author: RounakDhillon

collate-ai/sql-agent.mdx

@@ -51,3 +51,25 @@ After clicking the icon, you will be redirected to the Ask Collate interface.
 In Ask Collate, type your question or request.
 
 You can ask anything related to SQL query creation, optimization, explanations, or filters.
+
+<img noZoom src="/public/images/collate-ai/collate-ai-sql-agent-feature.png" alt="update or suggest tiers" />
+
+## Setup Instructions
+
+1. **Navigate to Applications**: Go to `Settings > Applications`.
+
+<img noZoom src="/public/images/collate-ai/collate-ai-agent.png" alt="setting up Collate AI" />
+
+2. **Install the Agent**: Click on "Add Apps" to access the marketplace and install the Collate AI Tier Agent.
+
+<img noZoom src="/public/images/collate-ai/collate-ai-sql-agent.png" alt="Installation" />
+
+3. **Configure the Agent**:
+   - **Filter**: Use the UI Query Filter builder to select assets for tier classification.
+   - **Patch Tier If Empty**: Enable this option to automatically assign a tier to assets that currently lack one.
+
+<img noZoom src="/public/images/collate-ai/collate-ai-tier-agent1.png" alt="Configuration" />
+
+4. **Scheduling**: Set up regular intervals for the agent to run and update metadata.
+
+<img noZoom src="/public/images/collate-ai/collate-ai-tier-agent2.png" alt="Scheduling" />

collate-menu.mdx

@@ -1964,9 +1964,9 @@ site_menu:
     url: /main-concepts/metadata-standard/schemas/security/credentials/gcpvalues
   - category: Main Concepts / Metadata Standard / Schemas / Security / Credentials / GitCredentials
     url: /main-concepts/metadata-standard/schemas/security/credentials/gitcredentials
-  - category: Main Concepts / Metadata Standard / Schemas / Security / Credentials / GithubCredentials
+  - category: Main Concepts / Metadata Standard / Schemas / Security / Credentials / GitHubCredentials
     url: /main-concepts/metadata-standard/schemas/security/credentials/githubcredentials
-  - category: Main Concepts / Metadata Standard / Schemas / Security / Credentials / GitlabCredentials
+  - category: Main Concepts / Metadata Standard / Schemas / Security / Credentials / GitLabCredentials
     url: /main-concepts/metadata-standard/schemas/security/credentials/gitlabcredentials
   - category: Main Concepts / Metadata Standard / Schemas / Security / Credentials
     url: /main-concepts/metadata-standard/schemas/security/credentials

connectors/api/rest/index.mdx

@@ -23,7 +23,7 @@ Configure and schedule REST metadata workflows from the OpenMetadata UI:
 - [Troubleshooting](/connectors/api/rest/troubleshooting)
 ## Requirements
 ### Generate OpenAPI Schema URL
-- Generate OpenAPI schema url for your service[OpenAPI spec](https://swagger.io/specification/#openapi-document)
+- Generate OpenAPI schema URL for your service[OpenAPI spec](https://swagger.io/specification/#openapi-document)
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"REST"} selectServicePath={"/public/images/connectors/rest/select-service.png"} addNewServicePath={"/public/images/connectors/rest/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/rest/service-connection.png"} />
 #### Connection Options

connectors/api/rest/yaml.mdx

@@ -30,7 +30,7 @@ Configure and schedule REST metadata workflows from the OpenMetadata UI:
 ### Python Requirements
 <PythonRequirements />
 ### Generate OpenAPI Schema URL
-- Generate OpenAPI schema url for your service[OpenAPI spec](https://swagger.io/specification/#openapi-document)
+- Generate OpenAPI schema URL for your service[OpenAPI spec](https://swagger.io/specification/#openapi-document)
 ## Metadata Ingestion
 ### 1. Define the YAML Config
 

…ashboard/powerbi-report-server/index.mdx …/dashboard/powerbireportserver/index.mdxconnectors/dashboard/powerbi-report-server/index.mdx renamed to connectors/dashboard/powerbireportserver/index.mdx connectors/dashboard/powerbi-report-server/index.mdx renamed to connectors/dashboard/powerbireportserver/index.mdx

@@ -6,7 +6,6 @@ sidebarTitle: Overview
 ---
 import ReverseMetadata from '/snippets/connectors/database/databricks/reverse-metadata.mdx'
 import { ConnectorDetailsHeader } from '/snippets/components/ConnectorDetailsHeader/ConnectorDetailsHeader.jsx'
-import PythonRequirements from '/snippets/connectors/python-requirements.mdx'
 import ExternalIngestionDeployment from '/snippets/connectors/external-ingestion-deployment.mdx'
 import TestConnection from '/snippets/connectors/test-connection.mdx'
 import IngestionScheduleAndDeploy from '/snippets/connectors/ingestion-schedule-and-deploy.mdx'
@@ -22,7 +21,7 @@ stage="PROD"
 availableFeatures={["Metadata", "Query Usage", "Lineage", "Column-level Lineage", "Data Profiler", "Data Quality", "dbt", "Sample Data", "Reverse Metadata (Collate Only)", "Auto-Classification"]}
 unavailableFeatures={["Stored Procedures", "Tags", "Owners"]} />
 <Tip>
-As per the [documentation](https://docs.databricks.com/en/data-governance/unity-catalog/tags.html#manage-tags-with-sql-commands) here, note that we only support metadata `tag` extraction for databricks version 13.3 version and higher.
+As per the [documentation](https://docs.databricks.com/en/data-governance/unity-catalog/tags.html#manage-tags-with-sql-commands) here, note that we only support metadata `tag` extraction for Databricks version 13.3 version and higher.
 </Tip>
 In this section, we provide guides and references to use the Databricks connector.
 Configure and schedule Databricks metadata and profiler workflows from the OpenMetadata UI:
@@ -38,12 +37,6 @@ Configure and schedule Databricks metadata and profiler workflows from the OpenM
 - [Reverse Metadata](#reverse-metadata)
 <ExternalIngestionDeployment />
 ## Requirements
-### Python Requirements
-<PythonRequirements />
-To run the Databricks ingestion, you will need to install:
-```bash
-pip3 install "openmetadata-ingestion[databricks]"
-```
 ### Permission Requirement
 To enable full functionality of metadata extraction, profiling, usage, and lineage features in OpenMetadata, the following permissions must be granted to the relevant users in your Databricks environment.
 ### Metadata and Profiling Permissions
@@ -65,7 +58,7 @@ These permissions allow access to Databricks system tables that track query acti
 Adjust &lt;user&gt;, &lt;catalog_name&gt;, &lt;schema_name&gt;, and &lt;table_name&gt; according to your specific deployment and security requirements.
 </Tip>
 ## Unity Catalog
-If you are using unity catalog in Databricks, then checkout the [Unity Catalog](/connectors/database/unity-catalog) connector.
+If you are using Unity Catalog in Databricks, then checkout the [Unity Catalog](/connectors/database/unity-catalog) connector.
 ## Metadata Ingestion
 <MetadataIngestionUi connector={"Databricks"} selectServicePath={"/public/images/connectors/databricks/select-service.png"} addNewServicePath={"/public/images/connectors/databricks/add-new-service.png"} serviceConnectionPath={"/public/images/connectors/databricks/service-connection.png"} />
 # Connection Details

…owerbi-report-server/troubleshooting.mdx …/powerbireportserver/troubleshooting.mdxconnectors/dashboard/powerbi-report-server/troubleshooting.mdx renamed to connectors/dashboard/powerbireportserver/troubleshooting.mdx connectors/dashboard/powerbi-report-server/troubleshooting.mdx renamed to connectors/dashboard/powerbireportserver/troubleshooting.mdx

@@ -29,7 +29,7 @@ stage="PROD"
 availableFeatures={["Metadata", "Query Usage", "Lineage", "Column-level Lineage", "Data Profiler", "Data Quality", "dbt", "Sample Data", "Reverse Metadata (Collate Only)", "Auto-Classification"]}
 unavailableFeatures={["Stored Procedures", "Tags", "Owners"]} />
 <Tip>
-As per the [documentation](https://docs.databricks.com/en/data-governance/unity-catalog/tags.html#manage-tags-with-sql-commands) here, note that we only support metadata `tag` extraction for databricks version 13.3 version and higher.
+As per the [documentation](https://docs.databricks.com/en/data-governance/unity-catalog/tags.html#manage-tags-with-sql-commands) here, note that we only support metadata `tag` extraction for Databricks version 13.3 version and higher.
 </Tip>
 In this section, we provide guides and references to use the Databricks connector.
 Configure and schedule Databricks metadata and profiler workflows from the OpenMetadata UI:

…dashboard/powerbi-report-server/yaml.mdx …s/dashboard/powerbireportserver/yaml.mdxconnectors/dashboard/powerbi-report-server/yaml.mdx renamed to connectors/dashboard/powerbireportserver/yaml.mdx connectors/dashboard/powerbi-report-server/yaml.mdx renamed to connectors/dashboard/powerbireportserver/yaml.mdx

@@ -41,7 +41,7 @@ This applies **only to fields marked as secrets** in the connection form (these
 For a complete guide on managing secrets in hybrid setups, see the [Hybrid Ingestion Runner Secret Management Guide](https://docs.getcollate.io/getting-started/day-1/hybrid-saas/hybrid-ingestion-runner#3.-manage-secrets-securely).
 </Tip>
 - **Host and Port**: This parameter specifies the host and port of the SAP ERP instance. This should be specified as a string in the format `https://hostname.com`.
-- **API Key**: Api Key to authenticate the SAP ERP Apis.
+- **API Key**: API Key to authenticate the SAP ERP APIs.
 - **database**: Optional name to give to the database in OpenMetadata. If left blank, we will use `default` as the database name.
 - **databaseSchema**: Optional name to give to the database schema in OpenMetadata. If left blank, we will use `default` as the database schema name.
 - **paginationLimit**: Pagination limit used while querying the SAP ERP APIs for fetching the entities.