Interface CfnPolicyStoreProps
- All Superinterfaces:
software.amazon.jsii.JsiiSerializable
- All Known Implementing Classes:
CfnPolicyStoreProps.Jsii$Proxy
CfnPolicyStore
.
Example:
// The code below shows an example of how to instantiate this type. // The values are placeholders you should change. import software.amazon.awscdk.services.verifiedpermissions.*; CfnPolicyStoreProps cfnPolicyStoreProps = CfnPolicyStoreProps.builder() .validationSettings(ValidationSettingsProperty.builder() .mode("mode") .build()) // the properties below are optional .description("description") .schema(SchemaDefinitionProperty.builder() .cedarJson("cedarJson") .build()) .build();
- See Also:
-
Nested Class Summary
Nested ClassesModifier and TypeInterfaceDescriptionstatic final class
A builder forCfnPolicyStoreProps
static final class
An implementation forCfnPolicyStoreProps
-
Method Summary
Modifier and TypeMethodDescriptionstatic CfnPolicyStoreProps.Builder
builder()
default String
Descriptive text that you can provide to help with identification of the current policy store.default Object
Creates or updates the policy schema in a policy store.Specifies the validation setting for this policy store.Methods inherited from interface software.amazon.jsii.JsiiSerializable
$jsii$toJson
-
Method Details
-
getValidationSettings
Specifies the validation setting for this policy store.Currently, the only valid and required value is
Mode
.We recommend that you turn on
STRICT
mode only after you define a schema. If a schema doesn't exist, thenSTRICT
mode causes any policy to fail validation, and Verified Permissions rejects the policy. You can turn off validation by using the UpdatePolicyStore . Then, when you have a schema defined, use UpdatePolicyStore again to turn validation back on.- See Also:
-
getDescription
Descriptive text that you can provide to help with identification of the current policy store.- See Also:
-
getSchema
Creates or updates the policy schema in a policy store.Cedar can use the schema to validate any Cedar policies and policy templates submitted to the policy store. Any changes to the schema validate only policies and templates submitted after the schema change. Existing policies and templates are not re-evaluated against the changed schema. If you later update a policy, then it is evaluated against the new schema at that time.
- See Also:
-
builder
- Returns:
- a
CfnPolicyStoreProps.Builder
ofCfnPolicyStoreProps
-