Update an error msg to avoid potential confusion (#864)

* update error message regarding a state version still being processed. Before the msg did not include the word state, so a customer, who had no resources in the workspace, misinterpret the msg and thought that it was saying that he had resources in the workspace and they were being processed
hashicorp · Mar 8, 2024 · 418463a · 418463a
1 parent 98aea87
commit 418463a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 1 deletion.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,8 @@
 # Unreleased
 
+## Bug fixes
+* Change the error message for `ErrWorkspaceStillProcessing` to be the same error message returned by the API by @uturunku1 [#864](https://github.com/hashicorp/go-tfe/pull/864)
+
 # v1.47.0
 
 ## Enhancements

diff --git a/errors.go b/errors.go
@@ -66,7 +66,7 @@ var (
 	// to determine if it is safe to delete. "conflict" followed by newline is used to
 	// preserve go-tfe version compatibility with the error constructed at runtime before it was
 	// defined here.
-	ErrWorkspaceStillProcessing = errors.New("conflict\nworkspace is still being processed to discover resources")
+	ErrWorkspaceStillProcessing = errors.New("conflict\nLatest workspace state is being processed to discover resources, please try again later")
 
 	// ErrWorkspaceNotSafeToDelete is returned when a workspace has processed state and
 	// is determined to still have resources present. "conflict" followed by newline is used to