blib/lib/Paws/IoTSiteWise/UpdateGatewayCapabilityConfigurationResponse.pm untested

filter: Statementstmt 0.0% 0 / 8 Branchbran n/a Conditioncond n/a MC/DCmcdc n/a Subroutinesub 0.0% 0 / 1 Podpod n/a totaltotal 0.0% 0 / 9 CC 1 SCAR 6.9
CC
1
Cov
0%
BEGIN
2.0
CRAP 2.0
1  
2 package Paws::IoTSiteWise::UpdateGatewayCapabilityConfigurationResponse;
3 use Moose;
4 has CapabilityNamespace => (is => 'ro', isa => 'Str', traits => ['NameInRequest'], request_name => 'capabilityNamespace', required => 1);
5 has CapabilitySyncStatus => (is => 'ro', isa => 'Str', traits => ['NameInRequest'], request_name => 'capabilitySyncStatus', required => 1);
6  
7 has _request_id => (is => 'ro', isa => 'Str');
8 1;
9  
10 ### main pod documentation begin ###
11  
12 =head1 NAME
13  
14 Paws::IoTSiteWise::UpdateGatewayCapabilityConfigurationResponse
15  
16 =head1 ATTRIBUTES
17  
18  
19 =head2 B<REQUIRED> CapabilityNamespace => Str
20  
21 The namespace of the gateway capability.
22  
23  
24 =head2 B<REQUIRED> CapabilitySyncStatus => Str
25  
26 The synchronization status of the capability configuration. The sync
27 status can be one of the following:
28  
29 =over
30  
31 =item *
32  
33 C<IN_SYNC> E<ndash> The gateway is running the capability
34 configuration.
35  
36 =item *
37  
38 C<OUT_OF_SYNC> E<ndash> The gateway hasn't received the capability
39 configuration.
40  
41 =item *
42  
43 C<SYNC_FAILED> E<ndash> The gateway rejected the capability
44 configuration.
45  
46 =back
47  
48 After you update a capability configuration, its sync status is
49 C<OUT_OF_SYNC> until the gateway receives and applies or rejects the
50 updated configuration.
51  
52 Valid values are: C<"IN_SYNC">, C<"OUT_OF_SYNC">, C<"SYNC_FAILED">
53 =head2 _request_id => Str
54  
55  
56 =cut
57