From cfc627367c6d1f2023194cf31c162a5f332d56d7 Mon Sep 17 00:00:00 2001
From: Vikram Sahu <vikram.sahu@harness.io>
Date: Wed, 19 Nov 2025 17:34:39 +0530
Subject: [PATCH 1/2] Update important note

---
 docs/resources/platform_apikey.md          | 25 ++++++++++++++++++++
 docs/resources/platform_service_account.md | 26 +++++++++++++++++++++
 docs/resources/platform_token.md           | 27 ++++++++++++++++++++++
 3 files changed, 78 insertions(+)

diff --git a/docs/resources/platform_apikey.md b/docs/resources/platform_apikey.md
index 2fdbc4388..8e656f76e 100644
--- a/docs/resources/platform_apikey.md
+++ b/docs/resources/platform_apikey.md
@@ -67,6 +67,31 @@ resource "harness_platform_apikey" "test" {
 
 - `id` (String) The ID of this resource.
 
+### Important Note: Managing resource dependency order.
+
+Terraform determines deletion order based on resource dependencies. To avoid unexpected behavior, it’s recommended to define explicit `depends_on` blocks so resources are created and destroyed in the correct sequence.
+
+The expected order is:
+
+* **Create:** Service Account → API Key → Token
+* **Destroy:** Token → API Key → Service Account
+
+You can enforce this explicitly in your Terraform configuration:
+
+```terraform
+resource "harness_platform_token" "token" {
+  ...
+  depends_on = [harness_platform_apikey.apikey]
+}
+
+resource "harness_platform_apikey" "apikey" {
+  ...
+  depends_on = [harness_platform_service_account.service_account]
+}
+```
+
+This ensures Terraform manages these resources in the proper order during both creation and deletion.
+
 ## Import
 
 Import is supported using the following syntax:
diff --git a/docs/resources/platform_service_account.md b/docs/resources/platform_service_account.md
index 6fd334166..1fcab4bbc 100644
--- a/docs/resources/platform_service_account.md
+++ b/docs/resources/platform_service_account.md
@@ -44,6 +44,31 @@ resource "harness_platform_service_account" "example" {
 
 - `id` (String) The ID of this resource.
 
+### Important Note: Managing resource dependency order.
+
+Terraform determines deletion order based on resource dependencies. To avoid unexpected behavior, it’s recommended to define explicit `depends_on` blocks so resources are created and destroyed in the correct sequence.
+
+The expected order is:
+
+* **Create:** Service Account → API Key → Token
+* **Destroy:** Token → API Key → Service Account
+
+You can enforce this explicitly in your Terraform configuration:
+
+```terraform
+resource "harness_platform_token" "token" {
+  ...
+  depends_on = [harness_platform_apikey.apikey]
+}
+
+resource "harness_platform_apikey" "apikey" {
+  ...
+  depends_on = [harness_platform_service_account.service_account]
+}
+```
+
+This ensures Terraform manages these resources in the proper order during both creation and deletion.
+
 ## Import
 
 Import is supported using the following syntax:
@@ -60,3 +85,4 @@ terraform import harness_platform_service_account.example <ord_id>/<service_acco
 # Import project level service account
 terraform import harness_platform_service_account.example <org_id>/<project_id>/<service_account_id>
 ```
+
diff --git a/docs/resources/platform_token.md b/docs/resources/platform_token.md
index d266fe1e4..73d6255ee 100644
--- a/docs/resources/platform_token.md
+++ b/docs/resources/platform_token.md
@@ -78,6 +78,31 @@ resource "harness_platform_token" "test" {
 - `id` (String) The ID of this resource.
 - `value` (String, Sensitive) Value of the Token
 
+### Important Note: Managing resource dependency order.
+
+Terraform determines deletion order based on resource dependencies. To avoid unexpected behavior, it’s recommended to define explicit `depends_on` blocks so resources are created and destroyed in the correct sequence.
+
+The expected order is:
+
+* **Create:** Service Account → API Key → Token
+* **Destroy:** Token → API Key → Service Account
+
+You can enforce this explicitly in your Terraform configuration:
+
+```terraform
+resource "harness_platform_token" "token" {
+  ...
+  depends_on = [harness_platform_apikey.apikey]
+}
+
+resource "harness_platform_apikey" "apikey" {
+  ...
+  depends_on = [harness_platform_service_account.service_account]
+}
+```
+
+This ensures Terraform manages these resources in the proper order during both creation and deletion.
+
 ## Import
 
 Import is supported using the following syntax:
@@ -94,3 +119,5 @@ terraform import harness_platform_token <org_id>/<parent_id>/<apikey_id>/<apikey
 # Import project level token
 terraform import harness_platform_token <org_id>/<project_id>/<parent_id>/<apikey_id>/<apikey_type>/<token_id>
 ```
+
+

From 564f960099574cf65d4fec72a39f26ffb41d71c7 Mon Sep 17 00:00:00 2001
From: Vikram Sahu <vikram.sahu@harness.io>
Date: Wed, 19 Nov 2025 17:36:51 +0530
Subject: [PATCH 2/2] remove extra space

---
 docs/resources/platform_token.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/docs/resources/platform_token.md b/docs/resources/platform_token.md
index 73d6255ee..854be079b 100644
--- a/docs/resources/platform_token.md
+++ b/docs/resources/platform_token.md
@@ -118,6 +118,4 @@ terraform import harness_platform_token <org_id>/<parent_id>/<apikey_id>/<apikey
 
 # Import project level token
 terraform import harness_platform_token <org_id>/<project_id>/<parent_id>/<apikey_id>/<apikey_type>/<token_id>
-```
-
-
+```
\ No newline at end of file