From 8b8991b8528cdfae679630c5a13d7e2a5e6917ca Mon Sep 17 00:00:00 2001 From: Scott Andrews Date: Tue, 27 Feb 2024 12:44:19 -0500 Subject: [PATCH] Clarify binding name collisions Because service bindings are inherently decentralized, there is no way to universally detect a name collision. Users are encouraged to avoid colliding names as the behavior is undefined by the spec. Implementations may check for known collisions to display a more meaningful to the user, but detection cannot be guaranteed as it's at best a good faith attempt. Signed-off-by: Scott Andrews --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 8164bfc..affa787 100644 --- a/README.md +++ b/README.md @@ -206,6 +206,8 @@ The name of a binding entry file name **SHOULD** match `[a-z0-9\-\.]{1,253}`. T The collection of files within the directory **MAY** change during the lifetime of the container or between container launches. +Users **SHOULD** ensure each binding has a unique name. The behavior for name collisions is undefined. Implementations **MAY** attempt a good faith check for collisions to provide a meaningful error message. + ## Example Directory Structure ```plain