Add note on resource name conflicts (#222)

* Add note on resource names * Update docs/content/reference/limitations.md Co-authored-by: Emily Potyraj (Watkins) <[email protected]> * Review feedback Co-authored-by: Emily Potyraj (Watkins) <[email protected]>
radius-project · Aug 4, 2022 · 00e28eb · 00e28eb
1 parent a4821cc
commit 00e28eb
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/docs/content/reference/limitations.md b/docs/content/reference/limitations.md
@@ -6,6 +6,16 @@ description: "Learn where there are known issues and limitations with the latest
 weight: 998
 ---
 
+## Radius resources
+
+### Resource names must be unique for a given resource type across applications
+
+Resources for a given type must currently have unique names within an environment, even across applications. For example, if two applications both have a `frontend` container resource, the first application deployment will succeed while the second will fail.
+
+As a workaround, use separate environments for applications that have repeated resource names for a given type.
+
+This will be addressed further in a future release.
+
 ## Bicep & Deployment Engine
 
 ### Currently using a forked version of Bicep