-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Consider a store with following sample content:
proj1/foo
proj2/foo
foo
Possible generic scoping rules we could impose:
Prefix scoping: docker/mcp/** -> **
docker/mcp/foo
docker/mcp/proj1/foo
docker/mcp/proj2/foo
Wrap scoping:
docker/*/mcp/* -> */*
docker/foo/mcp (not a match)
docker/proj1/mcp/foo
docker/proj2/mcp/foo
docker/**/mcp -> **
Queries:
docker/proj1/foo/mcp -> proj1/foo
docker/foo/mcp -> foo
docker/**/mcp/* -> **/*
Queries:
docker/proj1/foo/mcp/day1 -> proj1/foo/day1
docker/mcp/day1 -> day1
docker/*/mcp/** -> */**
docker/**/mcp/** -> **/** -> ** -> illegal scoping rule
docker/*/**/mcp/**/* -> */**/**/* -> */**/* -> illegal scoping rule
docker/*/**/mcp/*/** -> */**/*/** -> */*/** -> illegal scoping rule
Scoping algorithm:
- must be a valid pattern
- compute the forwarded pattern
- verify if the forwarded pattern does not have any redundancy
- If redundancy: ambiguous scoping rule -> error
- If no redundancy: unique scoping rule -> pass
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels