/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.verifiedpermissions.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.AmazonWebServiceRequest; /** * * @see AWS API Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class CreatePolicyStoreRequest extends com.amazonaws.AmazonWebServiceRequest implements Serializable, Cloneable { /** *
* Specifies a unique, case-sensitive ID that you provide to ensure the idempotency of the request. This lets you * safely retry the request without accidentally performing the same operation a second time. Passing the same value * to a later call to an operation requires that you also pass the same value for all other parameters. We recommend * that you use a UUID type of value.. *
** If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the retry fails
* with an IdempotentParameterMismatch
error.
*
* 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,
* then STRICT
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.
*
* Specifies a unique, case-sensitive ID that you provide to ensure the idempotency of the request. This lets you * safely retry the request without accidentally performing the same operation a second time. Passing the same value * to a later call to an operation requires that you also pass the same value for all other parameters. We recommend * that you use a UUID type of value.. *
** If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the retry fails
* with an IdempotentParameterMismatch
error.
*
* If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the
* retry fails with an IdempotentParameterMismatch
error.
*/
public void setClientToken(String clientToken) {
this.clientToken = clientToken;
}
/**
*
* Specifies a unique, case-sensitive ID that you provide to ensure the idempotency of the request. This lets you * safely retry the request without accidentally performing the same operation a second time. Passing the same value * to a later call to an operation requires that you also pass the same value for all other parameters. We recommend * that you use a UUID type of value.. *
** If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the retry fails
* with an IdempotentParameterMismatch
error.
*
* If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the
* retry fails with an IdempotentParameterMismatch
error.
*/
public String getClientToken() {
return this.clientToken;
}
/**
*
* Specifies a unique, case-sensitive ID that you provide to ensure the idempotency of the request. This lets you * safely retry the request without accidentally performing the same operation a second time. Passing the same value * to a later call to an operation requires that you also pass the same value for all other parameters. We recommend * that you use a UUID type of value.. *
** If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the retry fails
* with an IdempotentParameterMismatch
error.
*
* If you don't provide this value, then Amazon Web Services generates a random one for you. *
*
* If you retry the operation with the same ClientToken
, but with different parameters, the
* retry fails with an IdempotentParameterMismatch
error.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public CreatePolicyStoreRequest withClientToken(String clientToken) {
setClientToken(clientToken);
return this;
}
/**
*
* 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,
* then STRICT
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.
*
* 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, then STRICT
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.
*
* 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,
* then STRICT
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.
*
* 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, then STRICT
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.
*
* 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,
* then STRICT
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.
*
* 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, then STRICT
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.
*