package Paws::Backup::GetBackupPlanFromJSON;
use Moose;
has BackupPlanTemplateJson => (is => 'ro', isa => 'Str', required => 1);
use MooseX::ClassAttribute;
class_has _api_call => (isa => '
Str', is => 'ro', default => 'GetBackupPlanFromJSON');
class_has _api_uri => (isa => 'Str', is => 'ro', default => '/backup/template/json/toPlan');
class_has _api_method => (isa => 'Str', is =>
:Backup::GetBackupPlanFromJSONOutput');
1;
### main pod documentation begin ###
=head1 NAME
Paws::Backup::GetBackupPlanFromJSON - Arguments for method GetBackupPlanFromJSON on L<Paws::Backup>
=hea
on where they are created. They consist of lowercase
letters, numbers, and hyphens.
=head2 Policy => Str
The backup vault access policy document in JSON format.
=head2 _request_id => Str
=cut
launch role, set to C<"AssumeRole":
"LAUNCH_ROLE">.
=item Parameters
The list of parameters in JSON format.
For example: C<[{\"Name\":\"InstanceId\",\"Type\":\"TARGET\"}]> or
C<[{\"Name\":\"Instan
ackup::BackupJob>]
An array of structures containing metadata about your backup jobs
returned in JSON format.
=head2 NextToken => Str
The next item following a partial list of returned items. For
L of the CloudFormation template in Amazon S3, in JSON format.
C<LoadTemplateFromURL>
Use the URL of the CloudFormation template in Amazon S3 in JSON format.
C<ImportFromPhysicalId>
Use the physic
<ImportFromPhysicalId>
]
The URL of the CloudFormation template in Amazon S3. Specify the URL in
JSON format as follows:
C<"LoadTemplateFromURL":
"https://s3.amazonaws.com/cf-templates-ozkq9d3hgiq2-
ntains
the template. Currently only supports CloudFormation stack arn. Specify
the physical id in JSON format as follows: C<ImportFromPhysicalId:
E<ldquo>arn:aws:cloudformation:[us-east-1]:[accountId]
etters, numbers, and hyphens.
=head2 Policy => Str
The backup vault access policy document in JSON format.
=head1 SEE ALSO
This class forms part of L<Paws>, documenting arguments for method P
=> {
}, # OPTIONAL
}, # OPTIONAL
FileFormatConfiguration => {
JsonConfiguration => {
}, # OPTIONAL
ParquetConfiguration => {
SchemaDef
tion of file formats. AWS IoT
Analytics data stores support JSON and Parquet
(https://parquet.apache.org/).
The default file format is JSON. You can specify only one format.
You can't change the fil
me { 'datapipeline' }
sub version { '2012-10-29' }
sub target_prefix { 'DataPipeline' }
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 ActivatePipeline {
my $self = shift;
my $call_object = $self->new_with_
Str
The identifier of the constraint.
=head2 Parameters => Str
The constraint parameters, in JSON format. The syntax depends on the
constraint type as follows:
=over
=item LAUNCH
You are requi
for each repeated request.
=head2 B<REQUIRED> Parameters => Str
The constraint parameters, in JSON format. The syntax depends on the
constraint type as follows:
=over
=item LAUNCH
You are requi
s::Backup::CopyJob>]
An array of structures containing metadata about your copy jobs
returned in JSON format.
=head2 NextToken => Str
The next item following a partial list of returned items. For
ad2 AlarmHistoryItems => ArrayRef[L<Paws::CloudWatch::AlarmHistoryItem>]
The alarm histories, in JSON format.
=head2 NextToken => Str
The token that marks the start of the next batch of returned r
ipal>, you grant permission to all the
accounts in the named organization.
The C<Condition> is a JSON string which must contain C<Type>, C<Key>,
and C<Value> fields.
=head2 EventBusName => Str
Th
ciated with the rule. If you omit this,
the default event bus is used.
=head2 Policy => Str
A JSON string that describes the permission policy statement. You can
include a C<Policy> parameter in t
=head1 ATTRIBUTES
=head2 InputPathsMap => L<Paws::CloudWatchEvents::TransformerPaths>
Map of JSON paths to be extracted from the event. You can then insert
these in the template in C<InputTemplat
hsMap> is an array key-value pairs, where each value is a
valid JSON path. You can have as many as 100 key-value pairs. You must
use JSON dot notation, not bracket notation.
The keys cannot start wit
tPathsMaps> value in brackets:
E<lt>I<value>E<gt> The InputTemplate must be valid JSON.
If C<InputTemplate> is a JSON object (surrounded by curly braces), the
following restrictions apply:
=over
=i
d by an SaaS partner.
=head1 ATTRIBUTES
=head2 Detail => Str
A valid JSON string. There is no other schema imposed. The JSON string
may contain fields and nested subobjects.
=head2 DetailType =>
vent to be submitted.
=head1 ATTRIBUTES
=head2 Detail => Str
A valid JSON string. There is no other schema imposed. The JSON string
may contain fields and nested subobjects.
=head2 DetailType =>
IBUTES
=head2 B<REQUIRED> DashboardBody => Str
The detailed information about the dashboard in JSON format, including
the widgets to include and their location on the dashboard. This
parameter is r
rn>
=head1 ATTRIBUTES
=head2 B<REQUIRED> Event => Str
The event, in JSON format, to test against the event pattern. The JSON
must follow the format specified in AWS Events
(https://docs.aws.amazon
ent type.
Valid Values: text/plain | text/css | text/html |
application/javascript | application/json
=head2 MessageBody => Str
The message.
=head2 B<REQUIRED> StatusCode => Str
The HTTP respon