Skip to content

💡 [REQUEST] - Remove explicit key versioning from access conditions #186

@john-cremit

Description

@john-cremit

Is there an existing issue for this?

  • I have searched the existing issues

Reference Issues

#185

Problem

No response

Describe the solution you'd like

Previously, Access Conditions required explicit versioning in their attributes, such as attr=val@<namespace>#<version>. (See: #185)

To further streamline this, we want to eliminate the need for explicit key versioning in access conditions. Instead of having users write something like ("dept=IT@Akp#1" || "dept=IT@Bkp#3"), we’ll allow them to omit the version, resulting in ("dept=IT@Akp" || "dept=IT@Bkp").

Under the hood, the backbone will automatically incorporate the current key versions into the evaluation logic. For instance, the system would internally transform the condition into:
("dept=IT@Akp" || "dept=IT@Bkp") && ("Akp=1" && "Bkp=3")

This means the user never has to worry about version numbers when writing Access Conditions.

Additional context

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions