Module cedar_policy_core::ast
source · Expand description
This module contains the AST datatypes.
Structs§
- A borrowed version of LiteralPolicy exclusively for serialization
- While
RestrictedExpr
wraps an ownedExpr
,BorrowedRestrictedExpr
wraps a borrowedExpr
, with the same invariants. Context
field of aRequest
- EID type is just a SmolStr for now
- Entity datatype
- Unique ID for an entity. These represent entities in the AST.
- Internal AST for expressions used by the policy evaluator. This structure is a wrapper around an
ExprKind
, which is the expression variant this object contains. It also contains source information about where the expression was written in policy source code, and some generic data which is stored on each node of the AST. Cloning is O(1). - Builder for constructing
Expr
objects annotated with somedata
(possibly taking default value) and optional somesource_info
. - This structure implements the iterator used to traverse subexpressions of an expression.
- A new type wrapper around
Expr
that providesEq
andHash
implementations that ignore any source information or other generic data used to annotate theExpr
. - Cedar extension.
- Extension function. These can be called by the given
name
in Ceder expressions. - Object container for extension values, also stores the fully reduced AST for the arguments
- Identifiers. Anything in
Id
should be a valid identifier (and not contain, for instance, spaces or characters like ‘+’). - Represents either an static policy or a template linked policy This is the serializable version because it simply refers to the Template by its Id;
- This is the
Name
type used to name types, functions, etc. The name can include namespaces. Clone is O(1). - Represent a pattern literal (the RHS of the like operator) Also provides an implementation of the Display trait as well as a wildcard matching method.
- A Policy that contains: a pointer to its template an link ID (unless it’s an static policy) the bound values for slots in the template
- A unique identifier for a policy statement
- Represents a set of
Policy
s - Template constraint on principal head variables
- Represents the request tuple <P, A, R, C> (see the Cedar design doc).
- Template constraint on resource head variables
- A few places in Core use these “restricted expressions” (for lack of a better term) which are in some sense the minimal subset of
Expr
required to express all possibleValue
s. - Like
ExprShapeOnly
, but for restricted expressions. Value
’s internal representation of aSet
- Identifier for a slot Clone is O(1).
- Static Policies are policy that do not come from templates. They have the same structure as a template definition, but cannot contain slots
- Top level structure for a policy template. Contains both the AST for template, and the list of open slots in the template.
- Policy datatype.
Enums§
- Constraint for action head variables. Action variables can be constrained to be in any variable in a list.
- Built-in operators with exactly two arguments
- Which “style” is a function call
- the Effect of a policy
- A reference to an EntityUID that may be a Slot
- We support two types of entities. The first is a nominal type (e.g., User, Action) and the second is an unspecified type, which is used (internally) to represent cases where the input request does not provide a principal, action, and/or resource.
- An entry in a request for a Entity UID. It may either be a concrete EUID or an unknown in the case of partial evaluation
- The possible expression variants. This enum should be matched on by code recursively traversing the AST.
- The output of an extension call, either a value or an unknown
- Errors instantiating templates
- First-class values which may appear as literals in
Expr::Lit
. - An error that can be thrown converting an expression to a value
- Intermediate results of partial evaluation
- Represent an element in a pattern literal (the RHS of the like operation)
- Potential errors when working with
PolicySet
s. - Subset of AST variables that have the same constraint form
- Represents the constraints for principals and resources. Can either not constrain, or constrain via
==
orin
for a single entity literal. - Errors that can happen during policy reification
- Errors generated in the restricted_expr module
- Enum for errors encountered during substitution
- This represents the runtime type of a Cedar value. Nominal types: two entity types are equal if they have the same Name.
- Built-in operators with exactly one argument
- Error for unexpected slots
- This describes all the values which could be the dynamic result of evaluating an
Expr
. Cloning is O(1). - AST variables
Traits§
- Extension value.
- Extensions provide a type implementing
ExtensionValue
,Eq
, andOrd
. We automatically implementInternalExtensionValue
for that type (with the impl below). Internally, we usedyn InternalExtensionValue
instead ofdyn ExtensionValue
. - Trait for everything in Cedar that has a type known statically.
Functions§
- Collect an iterator of either residuals or values into one of the following a) An iterator over values, if everything evaluated to values b) An iterator over residuals expressions, if anything only evaluated to a residual Order is preserved.
- Arc::unwrap_or_clone() isn’t stabilized as of this writing, but this is its implementation
Type Aliases§
- Trait object that implements the extension function call.
- Map from Slot Ids to Entity UIDs which fill the slots