Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify binding name collisions #227

Merged
merged 1 commit into from
Mar 12, 2024
Merged

Conversation

scothis
Copy link
Contributor

@scothis scothis commented Feb 27, 2024

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.

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 <scott@andrews.me>
@scothis scothis merged commit 94bed11 into servicebinding:main Mar 12, 2024
1 check passed
@scothis scothis deleted the name-collision branch March 12, 2024 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants