blib/lib/Paws/SecretsManager/GetSecretValueResponse.pm untested

filter: Statementstmt 0.0% 0 / 11 Branchbran n/a Conditioncond n/a MC/DCmcdc n/a Subroutinesub 0.0% 0 / 1 Podpod n/a totaltotal 0.0% 0 / 12 CC 1 SCAR 6.9
CC
1
Cov
0%
BEGIN
2.0
CRAP 2.0
1  
2 package Paws::SecretsManager::GetSecretValueResponse;
3 use Moose;
4 has ARN => (is => 'ro', isa => 'Str');
5 has CreatedDate => (is => 'ro', isa => 'Str');
6 has Name => (is => 'ro', isa => 'Str');
7 has SecretBinary => (is => 'ro', isa => 'Str');
8 has SecretString => (is => 'ro', isa => 'Str');
9 has VersionId => (is => 'ro', isa => 'Str');
10 has VersionStages => (is => 'ro', isa => 'ArrayRef[Str|Undef]');
11  
12 has _request_id => (is => 'ro', isa => 'Str');
13  
14 ### main pod documentation begin ###
15  
16 =head1 NAME
17  
18 Paws::SecretsManager::GetSecretValueResponse
19  
20 =head1 ATTRIBUTES
21  
22  
23 =head2 ARN => Str
24  
25 The ARN of the secret.
26  
27  
28 =head2 CreatedDate => Str
29  
30 The date and time that this version of the secret was created.
31  
32  
33 =head2 Name => Str
34  
35 The friendly name of the secret.
36  
37  
38 =head2 SecretBinary => Str
39  
40 The decrypted part of the protected secret information that was
41 originally provided as binary data in the form of a byte array. The
42 response parameter represents the binary data as a base64-encoded
43 (https://tools.ietf.org/html/rfc4648#section-4) string.
44  
45 This parameter is not used if the secret is created by the Secrets
46 Manager console.
47  
48 If you store custom information in this field of the secret, then you
49 must code your Lambda rotation function to parse and interpret whatever
50 you store in the C<SecretString> or C<SecretBinary> fields.
51  
52  
53 =head2 SecretString => Str
54  
55 The decrypted part of the protected secret information that was
56 originally provided as a string.
57  
58 If you create this secret by using the Secrets Manager console then
59 only the C<SecretString> parameter contains data. Secrets Manager
60 stores the information as a JSON structure of key/value pairs that the
61 Lambda rotation function knows how to parse.
62  
63 If you store custom information in the secret by using the
64 CreateSecret, UpdateSecret, or PutSecretValue API operations instead of
65 the Secrets Manager console, or by using the B<Other secret type> in
66 the console, then you must code your Lambda rotation function to parse
67 and interpret those values.
68  
69  
70 =head2 VersionId => Str
71  
72 The unique identifier of this version of the secret.
73  
74  
75 =head2 VersionStages => ArrayRef[Str|Undef]
76  
77 A list of all of the staging labels currently attached to this version
78 of the secret.
79  
80  
81 =head2 _request_id => Str
82  
83  
84 =cut
85  
86 1;