[IDP] - identifier rules

docs/internal-developer-portal/catalog/catalog-yaml.md

@@ -110,7 +110,7 @@ Each kind represents a different type of entity within the Harness-native data m
 
 ### `identifier`
 
-The `identifier` field is a **unique, machine-readable** reference for the entity. It serves as the primary key for identifying and interacting with the entity.
+The `identifier` field is a **unique, machine-readable** reference for the entity. It serves as the primary key for identifying and interacting with the entity. Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
 
 | **Property**            | **Description**                                                                                       |
 |------------------------|-------------------------------------------------------------------------------------------------------|

docs/internal-developer-portal/catalog/manage-catalog.md

@@ -57,7 +57,7 @@ To create a new entity, navigate to the Harness IDP portal and click on **“Cre
 
     :::info
      **YAML validation** is performed to ensure compatibility with the **Harness-native Catalog YAML** model. Any errors will be shown in the Validation logs.
-
+    Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
     ![](./static/yaml-validation.png)
     :::
 
@@ -98,7 +98,7 @@ You can also use the [Catalog YAML](/docs/internal-developer-portal/catalog/cata
 ![](./static/yaml-conversion.png)
 
 :::info
-Note: **YAML validation** is automatically performed to ensure compatibility with the **Harness-native Catalog YAML model**. Any validation errors will be displayed in the Validation Logs.
+Note: **YAML validation** is automatically performed to ensure compatibility with the **Harness-native Catalog YAML model**. Any validation errors will be displayed in the Validation Logs. Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
 ![](./static/yaml-validation.png)
 :::
 

docs/internal-developer-portal/flows/harness-pipeline.md

@@ -512,6 +512,7 @@ spec:
   owner: test
   lifecycle: experimental
 ```
+> Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
 
 </TabItem>
 <TabItem value="YAML" label="YAML">

docs/internal-developer-portal/flows/manage-workflow-2o.md

@@ -75,7 +75,7 @@ Let's try creating a **Workflow** using both the methods:
   ![](./static/workflow-yaml.png)
 
   :::info
-  **Note:** **YAML validation** is performed to ensure compatibility with the **Harness-native Data Model**. Any errors will be shown in the Validation logs.
+  **YAML validation** is performed to ensure compatibility with the **Harness-native Data Model**. Any errors will be shown in the Validation logs. Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
   :::
 
   6. Once everything is set, click **“Create Workflow”** to finalize and create the Workflow.

docs/internal-developer-portal/get-started/catalog-2o.md

@@ -77,6 +77,8 @@ To create a **Component** via the UI:
 
 ![](./static/yaml-view.png)
 
+> ⚠️ **Note:** Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
+
   </TabItem>
 
   <TabItem value="YAML" label="Catalog YAML">
@@ -87,8 +89,11 @@ To create a Component using Catalog YAML:
 2. In the **Visual View**, switch to **YAML View** via the toggle at the top.
    ![](./static/yaml-way.png)
 3. Paste your existing Backstage YAML if available. Harness will auto-convert it into the native format.
+
    ![](./static/yaml-conversion.png)
 
+> ⚠️ **Note:** Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
+
 4. Define the **scope** of the entity in two ways: either switch to the Visual View and select the desired scope, or specify the **[projectIdentifier](/docs/internal-developer-portal/catalog/catalog-yaml.md#projectidentifier)** or **[orgIdentifier](/docs/internal-developer-portal/catalog/catalog-yaml.md#orgidentifier)** directly in the YAML to set the project or organization scope.
 ![](./static/scope-entity.png)
 5) Add any plugin configurations by including the relevant **annotations**.

docs/internal-developer-portal/idp-2o-overview/2-0-overview-and-upgrade-path.md

@@ -144,10 +144,10 @@ This approach is no longer supported in IDP 2.0. To align with the Harness platf
 
 This change ensures better alignment with GitX workflows and simplifies entity lifecycle management.
 
-> NOTE: This update also impacts the Git Experience documentation and onboarding flows. Ensure each service or entity has its own entity YAML file.
+> NOTE: This update also impacts the Git Experience documentation and onboarding flows. Ensure each service or entity has its own entity YAML file. Ensure your `identifier` follows [naming rules](https://developer.harness.io/docs/platform/references/entity-identifier-reference/#identifier-naming-rules). Invalid identifiers may lead to entity registration errors.
 
 :::note 
-Identifiers must use only letters, numbers, and underscores. Hyphens and special characters aren’t allowed.
+Identifiers must use only letters, numbers, and underscores. Hyphens and special characters aren’t allowed. 
 
 :::