ou
are initiating an inventory job and do not specify a Format field, JSON
is the default format. Valid values are "CSV" and "JSON".
=head2 InventoryRetrievalParameters => L<Paws::Glacier::Inventoryas not applied), or
InProgress (the policy is being applied now).
=head2 PolicyText => Str
The JSON text of the policy.
=head2 PolicyType => Str
The type of policy. Parameter Store supports the 'rekognition' }
sub version { '2016-06-27' }
sub target_prefix { 'RekognitionService' }
sub json_version { "1.1" }
has max_attempts => (is => 'ro', isa => 'Int', default => 5);
has retry =>
with 'Paws::API::Caller', 'Paws::API::EndpointResolver', 'Paws::Net::V4Signature', 'Paws::Net::JsonCaller';
sub CompareFaces {
my $self = shift;
my $call_object = $self->new_with_coerat describe attachments to a version of
a document.
=head2 B<REQUIRED> Content => Str
A valid JSON or YAML string.
=head2 DisplayName => Str
The friendly name of the Systems Manager document tfor the new document version. Systems
Manager supports JSON and YAML documents. JSON is the default format.
Valid values are: C<"YAML">, C<"JSON">, C<"TEXT">
=head2 DocumentVersion => Str
The versid1 ATTRIBUTES
=head2 ProvisionedCapacityList => ArrayRef[L<Paws::Glacier::ProvisionedCapacityDescription>]
The response body contains the following JSON fields.
=head2 _request_id => Str
=cut
t in the specified format. The document format can
be either JSON or YAML. JSON is the default format.
Valid values are: C<"YAML">, C<"JSON">, C<"TEXT">
=head2 DocumentVersion => Str
The document ve method is changed to C<POST> when a body is present.
=item * C<source>
The body is encoded as JSON and added to the query string as the C<source>
parameter. This has the advantage of still being );
=item C<serialize>
Whether the C<body> should be serialized in the standard way (as plain
JSON) or using the special I<bulk> format: C<"std"> or C<"bulk">.
=back
=head1 AUTHOR
Enrico ZimueAME
Paws::ECR::DeleteRepositoryPolicyResponse
=head1 ATTRIBUTES
=head2 PolicyText => Str
The JSON repository policy that was deleted from the repository.
=head2 RegistryId => Str
The registry ,
# optional
data => $body_as_string,
mime_type => 'application/json',
timeout => $timeout
});
Sends the request to the associated Elasticsearch nodeoperty, for all players who
are currently assigned to the game session. The matchmaker data is in
JSON syntax, formatted as a string. For more details, see Match Data
(https://docs.aws.amazon.com/gameQUIRED> RuleSetBody => Str
A collection of matchmaking rules, formatted as a JSON string. Comments
are not allowed in JSON, but most elements support a description field.
=head2 Tags => ArrayRef[Lages for each transport
protocol, set the value of the C<MessageStructure> parameter to C<json>
and use a JSON object for the C<Message> parameter.
Constraints:
=over
=item *
With the exception ofn is 1,600
characters.
=back
JSON-specific constraints:
=over
=item *
Keys in the JSON object that correspond to supported transport
protocols must have simple JSON string values.
=item *
The varsed (unescaped) before they are used in outgoing
messages.
=item *
Outbound notifications are JSON encoded (meaning that the characters
will be reescaped for sending).
=item *
Values have a mini SNS
retries failed deliveries to HTTP/S endpoints.
=item *
C<FilterPolicy> E<ndash> The simple JSON object that lets your
subscriber receive only a subset of messages, rather than receiving
every mdelivery to Amazon SQS or HTTP/S endpoints. This eliminates the need
for the endpoints to process JSON formatting, which is otherwise
created for Amazon SNS metadata.
=item *
C<RedrivePolicy> E<ndasSNS Developer Guide>.
=back
=head2 AttributeValue => Str
The new value for the attribute in JSON format.
=head2 B<REQUIRED> SubscriptionArn => Str
The ARN of the subscription to modify.
::CallerRole';
use Paws::Net::APIResponse;
use File::Slurper qw(read_text write_text);
use JSON::MaybeXS;
use Moose::Util::TypeConstraints;
use Path::Tiny;
use Paws::Net::FileMockCaller;
h $self->_test_file;
$file->parent->mkpath;
write_text($self->_test_file, encode_json({
request => {
params => $service->to_hash($call_object),
servi/www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1
# perl 5.6 ready UTF-8 encoding adapted from JSON::PP
our %escapes = map { chr($_) => sprintf("%%%02X", $_) } 0..255;
our $unsafe_char = qr/[^A-Za-
####################
### JSON parsers
### Heavily inspired by nuba++'s excellent Data::Printer::Filter::JSON
#############################################
sub _parse_json_boolean {
my ($value, web_json_true', '#ccffcc')
: ('filter_web_json_false', '#ffcccc')
);
return $ddp->maybe_colorize($value, @colors);
}
# JSON::NotString is from JSON::Parser (JSON 1.x)
filter 'JSON::NotString' => sub { _parse_json_boolean($_[0]->{value}, $_[1]) };
# JSON::Typist
filter 'JSON::Typist::String' => sub {
my ($obj, $ddp) = @_;
require Data::Printer::Common;
my $ret = Data::d.
=item *
C<DeliveryPolicy> E<ndash> The JSON serialization of the subscription's
delivery policy.
=item *
C<EffectiveDeliveryPolicy> E<ndash> The JSON serialization of the
effective delivery poldelivery
policy and account system defaults.
=item *
C<FilterPolicy> E<ndash> The filter policy JSON that is assigned to the
subscription. For more information, see Amazon SNS Message Filtering
(htt<ndash> C<true> if raw message delivery is
enabled for the subscription. Raw messages are free of JSON formatting
and can be sent to HTTP/S and Amazon SQS endpoints.
=item *
C<RedrivePolicy> E<ndash SNS
retries failed deliveries to HTTP/S endpoints.
=item *
C<FilterPolicy> E<ndash> The simple JSON object that lets your
subscriber receive only a subset of messages, rather than receiving
every mdelivery to Amazon SQS or HTTP/S endpoints. This eliminates the need
for the endpoints to process JSON formatting, which is otherwise
created for Amazon SNS metadata.
=item *
C<RedrivePolicy> E<ndas
=item *
For the C<email> protocol, the endpoint is an email address.
=item *
For the C<email-json> protocol, the endpoint is an email address.
=item *
For the C<sms> protocol, the endpoint is aQUIRED> RuleSetBody => Str
A collection of matchmaking rules, formatted as a JSON string. Comments
are not allowed in JSON, but most elements support a description field.
=head2 RuleSetName => Str
Str
Information about the matchmaking process that was used to create the
game session. It is in JSON syntax, formatted as a string. In addition
the matchmaking configuration used, it contains data o