asserts,confdb: have operators as a list in confdb-control assertion #15013
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a follow-up on last week's design sessions.
Internal Format
I've simplified the internal model to this:
This format works best with the
Delegate(operator, views, auth)
andUndelegate(operator, views, auth)
API as operations are done one operator at a time.The view's authentication is represented as a bitmask which allows us to easily update it with bitwise operations.
This simple representation allows us to avoid writing complex code that re-compacts the groups every time an update is made.
External Format
Once we're ready to output the assertion, it's serialized in the compact format prescribed by SD172:
Groups are loosely sorted by authentications: groups with
["operator-key"]
appear first, then groups with["store"]
only, and finally, groups with["operator-key", "store"]
. The fieldsgroup.operators
,group.authentications
, andgroup.views
are always sorted alphabetically.