Zyborg.Vault.POSH.xml

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
<?xml version="1.0"?>
<doc>
    <assembly>
        <name>Zyborg.Vault.POSH</name>
    </assembly>
    <members>
        <member name="T:Zyborg.Vault.POSH.DismountSecretProvider">
            <summary>
            <para type="synopsis">
            Disable an already-enabled auth provider.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>auth-disable</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Once the auth provider is disabled its path can no longer be used
            to authenticate.
            </para><para type="description">
            All access tokens generated via the disabled auth provider
            will be revoked.This command will block until all tokens are revoked.
            If the command is exited early the tokens will still be revoked.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.DismountSecretProvider.MountName">
            <summary>
            <para type="description">
            One or more paths at which auth providers are mounted.
            If an auth provider is mounted at multiple paths, each representing
            a different instance (with different configuration), this identifies
            the specific instance to disable.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.DismountAuthProvider">
            <summary>
            <para type="synopsis">Disable an already-enabled auth provider.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Once the auth provider is disabled its path can no longer be used
            to authenticate. All access tokens generated via the disabled auth provider
            will be revoked. This command will block until all tokens are revoked.
            If the command is exited early the tokens will still be revoked.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.DismountAuthProvider.MountName">
            <remarks>
            <para type="description">The name that identifies the mount point.</para>
            <para type="description">
            This should map to the <c>MountName</c> used for
            <c>Mount-AuthProvider</c>. If no <c>MountName</c> was provided
            when mounting, you should use the provider type (e.g. "file").
            </para>
            </remarks>
        </member>
        <member name="T:Zyborg.Vault.POSH.DismountAuditProvider">
            <summary >
            <para type="synopsis">Disable an audit provider.</para>
            </summary>
            <remarks>
            <para type="description">
            Once the audit backend is disabled no more audit logs will be sent to
            it. The data associated with the audit backend isn't affected.
            </para><para type="description">
            The <see cref="P:Zyborg.Vault.POSH.DismountAuditProvider.MountName"/> parameter should map to the
            <see cref="P:Zyborg.Vault.POSH.MountAuditProvider.MountName"/>used in
            <see cref="T:Zyborg.Vault.POSH.MountAuditProvider"/>. If no <c>MountName</c> was provided
            when mounting, you should use the provider type (e.g. "file").
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.DismountAuditProvider.MountName">
            <remarks>
            <para type="description">The name that identifies the mount point.</para>
            <para type="description">
            This should map to the <c>MountName</c> used for
            <c>Mount-AuditProvider</c>. If no <c>MountName</c> was provided
            when mounting, you should use the provider type (e.g. "file").
            </para>
            </remarks>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetAuthToken">
            <summary>
            <para type="synopsis">
            Retrieves information about tokens.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>token-lookup</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            You can use this command to retrieve a list of tokens, or
            to get information about specific tokens, either by their
            ID (token value) or the associated token 'accessor'.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuthToken.Token">
            <summary>
            <para type="description">
            The token ID to lookup.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuthToken.Accessor">
            <summary>
            <para type="description">
            The accessor of a token to lookup.
            </para><para type="description">
            Note that the response will not contain the token ID.
            Accessor is only meant for looking up the token properties.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuthToken.Self">
            <summary>
            <para type="description">
            Indicates to do a lookup of the currently authenticated token (lookup-self).
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuthToken.ListAccessors">
            <summary>
            <para type="description">
            Lists the accessors of existing tokens.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuthToken.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Internal.PSLambdaProperty`1">
            <summary>
            A specialization of a <see cref="T:System.Management.Automation.PSPropertyInfo"/> that supports defining
            getter and setter logic as lambdas.
            </summary>
        </member>
        <member name="M:Zyborg.Vault.POSH.Internal.PSLambdaProperty`1.#ctor(System.String,System.Func{`0},System.Action{`0})">
            <summary>
            Constructs with a name and a getter lambda, and an optional setter lambda.
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Internal.PSLambdaProperty`2">
            <summary>
            A specialization of a <see cref="T:System.Management.Automation.PSPropertyInfo"/> that supports defining
            getter and setter logic as lambdas that take a context argument.
            </summary>
        </member>
        <member name="M:Zyborg.Vault.POSH.Internal.PSLambdaProperty`2.#ctor(System.String,`1,System.Func{`1,`0},System.Action{`1,`0})">
            <summary>
            Constructs with a name and a getter lambda, and an optional setter lambda.
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Internal.PSLambdaMethod">
            <summary>
            A specialization of a <see cref="T:System.Management.Automation.PSMethodInfo"/> that supports defining
            the invocation handling logic as a lambda.
            </summary>
        </member>
        <member name="M:Zyborg.Vault.POSH.Internal.PSLambdaMethod.#ctor(System.String,System.Collections.Generic.IEnumerable{System.Type},System.Action{System.Object[]})">
            <summary>
            Constructs with a name and an invocation-handling lambda.
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Internal.PSLambdaMethod`1">
            <summary>
            A specialization of a <see cref="T:System.Management.Automation.PSMethodInfo"/> that supports defining
            the invocation handling logic as a lambda that returns a result.
            </summary>
        </member>
        <member name="M:Zyborg.Vault.POSH.Internal.PSLambdaMethod`1.#ctor(System.String,System.Collections.Generic.IEnumerable{System.Type},System.Func{System.Object[],`0})">
            <summary>
            Constructs with a name and an invocation-handling lambda that returns a result.
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Model.GetProfileResult">
            <summary>
            <para type="description">
            Captures the result of profile listing or retrieval from the
            user's profile store.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Model.InitializeResult">
            <summary>
            <para type="description">
            This class represents a container for the credentials returned from initializing
            a Vault instance.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This class is intentionally implemented in a non-straightforward way in order to
            capture and present all the contained elements in the best possible manner to the
            end user.
            </para><para type="description">
            If a user simply invokes the Init cmdlet without saving the returned output, the
            way this result object is defined will present to the user all of the elements
            such that they can be retroactively captured in a typical PS console. (I.e. they
            will not accidentally lose the returned unseal keys and the root token.)
            </para><para type="description">
            Otherwise if the result is captured to a variable, then all the individual elements
            will be accessible as normal as dynamic properties. Additionally the unseal keys
            can be accessed as a collection using a dynamically defined method.
            </para>
            </remarks>
        </member>
        <member name="T:Zyborg.Vault.POSH.Model.PathHelp">
            <summary>
            <para type="description">Captures help content for a given Vault path.</para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.Model.PathHelp.Help">
            <summary>
            <para type="description">Contains the help content.</para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.Model.PathHelp.SeeAlso">
            <summary>
            <para type="description">Reference to additional related help material.</para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Model.TokenAccessorList">
            <summary>
            <para type="description">
            Captures the list of keys representing authentication token accessors.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Model.TokenInfo">
            <summary>
            <para type="description">
            Captures details about authentication tokens.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Model.GenericAuditBackend">
            <summary>
            <para type="description">
            Captures details of a mounted audit provider.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.TestInstance">
            <summary>
            <para type="synopsis">
            Gets the initialization status of Vault.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This is an unauthenticated call and does not use a vault auth token.
            </para>
            </remarks>
        </member>
        <member name="T:Zyborg.Vault.POSH.MountAuthProvider">
            <summary>
            <para type="synopsis">Enable a new auth provider.</para>
            </summary>
            <remarks>
            <para type="description">
            This command enables a new auth provider. An auth provider is responsible
            for authenticating a user and assigning them policies with which they can
            access Vault.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuthProvider.Type">
            <summary>
            <para type="description">
            The type name of the auth provider (e.g. userpass).
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuthProvider.MountName">
            <summary>
            <para type="description">
            Mount point for the auth provider. This defaults
            to the type of the mount. This will make the auth
            provider available at <c>/auth/[path]</c>.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuthProvider.Description">
            <summary>
            <para type="description">
            Human-friendly description of the purpose of the
            auth provider. This shows up in the <c>Get-AuthMounts</c>.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuthProvider.Config">
            <summary>
            Optionally, specifies configuration values to apply to the enabled auth provider.
            </summary>
            <remarks>
            This option <i>assumes</i> that the authentication provider type supports a
            configuration child element name <c>config</c>. While many auth providers to
            conform to this pattern, some do not and require specialized configuration
            steps. <b>Please consult the documentation for each specific authentication
            provider type about its specific configuration requirements.</b>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuthProvider.Local">
            <summary>
            <para type="description">
            TODO: This flag is NOT currently supported.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetAuthMounts">
            <summary>
            <para type="synopsis">
            List the available auth provider mounts and auth methods.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'auth'</c> command with the <c>'-methods'</c> parameter.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuthMounts.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetAuditMounts">
            <summary>
            <para type="synopsis">
            List the enabled audit backends.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>audit-list</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            The output lists the mounted audit providers and the options for those
            providers. The options may contain sensitive information, and therefore
            only a root Vault user can view this.
            </para><para type="description">
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetAuditMounts.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetKeyStatus">
            <summary>
            <para type="synopsis">
            Provides information about the active encryption key.
            Specifically, the current key term and the key installation time.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>key-status</c> command.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetTokenCapabilities">
            <summary>
            <para type="synopsis">
            Fetch the capabilities of a token on a given path.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>capabilities</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            The capabilities can be fetched for a specific token ID, a
            token accessor or, if neither is provided, for the current
            user client token.
            </para><para type="description">
            If a token does not have any capability on a given path, or if any of the policies
            belonging to the token explicitly have["deny"] capability, or if the argument path
            is invalid, this command will respond with a ["deny"].
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetTokenCapabilities.Path">
            <summary>
            <para type="description">
            One or more paths to get capabilities for.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetTokenCapabilities.Token">
            <summary>
            <para type="description">
            The token ID to inquire capabilities for.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetTokenCapabilities.Accessor">
            <summary>
            <para type="description">
            The token accessor to inquire capabilities for.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetPolicy">
            <summary>
            <para type="synopsis">
            List the policies that are available or read a single policy.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>policies</c> command.
            This command lists the policies that are written to the Vault server.
            If a name of a policy is specified, that policy is outputted.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetPolicy.Name">
            <summary>
            <para type="description">
            The name of one or more policies to retrieve.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetSecretMounts">
            <summary>
            <para type="synopsis">
            Outputs information about the mounted secret providers.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>mounts</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This command lists the mounted secret providers, their mount points,
            the configured TTLs, and a human-friendly description of the mount point.
            </para><para type="description">
            A TTL of 'system' indicates that the system default is being used.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetSecretMounts.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.MountAuditProvider">
            <summary >
            <para type="synopsis">Enable an audit provider.</para>
            </summary>
            <remarks>
            <para type="description">
            This command enables an audit backend of type <c>Type</c>. Additional
            options for configuring the audit provider can be specified after the
            type in the same format as the <c>Write-Data</c> command in key/value pairs.
            </para><para type="description">
            For information on available configuration options, please see the
            documentation.
            </para>
            </remarks>
            <example>
            <para>
            To configure the file audit provider to write audit logs at the
            path c:\temp\log\audit.log:
            </para><code>
            ##
             
              PS> Mount-VltAuditProvider file -Config @{ file_path = "c:\temp\log\audit.log" }
            </code>
            </example>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuditProvider.Type">
            <summary>
            <para type="description">The type name of the audit provider (e.g. file).</para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuditProvider.MountName">
            <summary>
            <para type="description">
            Specify a unique path for this audit provider. This
            is purely for referencing this audit provider. By
            default this will be the backend type.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuditProvider.Config">
            <summary>
            <para type="description">
            One or more configuration key-value settings.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuditProvider.Description">
            <summary>
            <para type="description">
            A human-friendly description for the provider. This
            shows up only when querying the enabled providers.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountAuditProvider.Local">
            <summary>
            <para type="description">
            TODO: This flag is NOT currently supported.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.InitializeInstance">
            <summary>
            <para type="synopsis">
            Initialize a new Vault server.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>init</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This command connects to a Vault server and initializes it for the first time.
            This sets up the initial set of master keys and the backend data store structure.
            </para><para type="description">
            This command can't be called on an already-initialized Vault server.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.InitializeInstance.KeyShares">
            <summary>
            <para type="description">
            The number of key shares to split the master key into.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.InitializeInstance.KeyThreshold">
            <summary>
            <para type="description">
            The number of key shares required to reconstruct the master key.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.NewAuthToken">
            <summary>
            <para type="synopsis">
            Create a new auth token.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'token-create'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This command creates a new token that can be used for authentication.
            This token will be created as a child of your token.The created token
            will inherit your policies, or can be assigned a subset of your policies.
            </para>
            <para type="description">
            A lease can also be associated with the token.If a lease is not associated
            with the token, then it cannot be renewed.If a lease is associated with
            the token, it will expire after that amount of time unless it is renewed.
            </para>
            <para type="description">
            Metadata associated with the token(specified with "-metadata") is
            written to the audit log when the token is used.
            </para>
            <para type="description">
            If a role is specified, the role may override parameters specified here.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.Id">
            <summary>
            <para type="description">
            The token value that clients will use to authenticate with Vault.
            </para><para type="description">
            If not provided this defaults to a 36 character UUID.
            A root token is required to specify the ID of a token.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.DisplayName">
            <summary>
            <para type="description">
            A display name to associate with this token.
            </para><para type="description">
            This is a non-security sensitive value used to help
            identify created secrets, i.e.prefixes.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.InitialTtl">
            <summary>
            <para type="description">
            Initial TTL to associate with the token; renewals can extend this value.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.MaxTtl">
            <summary>
            <para type="description">
            An explicit maximum lifetime for the token. Unlike normal token TTLs,
            which can be renewed up until the maximum TTL set on the auth/token
            mount or the system configuration file, this lifetime is a hard limit
            set on the token itself and cannot be exceeded.
            </para><para type="description">
            This corresponds to the <c>'explicit-max-ttl'</c> vault CLI parameter.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.RenewalPeriod">
            <summary>
            <para type="description">
            TOOD: THIS PARAMETER IS CURRENTLY NOT SUPPORTED!
            </para>
            <para type="description">
            If specified, the token will be periodic; it will
            have no maximum TTL (unless a MaxTtl is
            also set) but every renewal will use the given
            period. Requires a root/sudo token to use.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.Renewable">
            <summary>
            <para type="description">
            Whether or not the token is renewable to extend its TTL up to Vault's
            configured maximum TTL for tokens.
            </para><para type="description">
            This defaults to true; set to false to disable renewal of this token.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.Metadata">
            <summary>
            <para type="description">
            Metadata to associate with the token.
            </para><para type="description">
            This shows up in the audit log.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.Orphan">
            <summary>
            <para type="description">
            If specified, the token will have no parent.
            </para><para type="description">
            This prevents the new token from being revoked with your token.
            Requires a root/sudo token to use.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.NoDefaultPolicy">
            <summary>
            <para type="description">
            If specified, the token will not have the "default"
            policy included in its policy set.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.Policy">
            <summary>
            <para type="description">
            One ore more policies to associate with this token.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.UseLimit">
            <summary>
            <para type="description">
            The number of times this token can be used until it is
            automatically revoked.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.Role">
            <summary>
            <para type="description">
            If set, the token will be created against the named role.
            </para><para type="description">
            The role may override other parameters. This requires
            the client to have permissions on the appropriate
            endpoint (auth/token/create/[name]).
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.WrapTtl">
            <summary>
            <para type="description">
            Indicates that the response should be wrapped in a
            cubbyhole token with the requested TTL.
            </para><para type="description">
            This is a numeric string with an optional suffix "s", "m", or "h";
            if no suffix is specified it will be parsed as seconds.
            </para><para type="description">
            The unwrapped response can be fetched by calling the command
            again but providing the wrapped token ID to the <c>UnwrapToken</c>
            parameter.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuthToken.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.RemovePolicy">
            <summary>
            <para type="synopsis">
            Delete a policy with the given name.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'policy-delete'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Once the policy is deleted, all users associated with the policy will
            be affected immediately. When a user is associated with a policy that
            doesn't exist, it is identical to not being associated with that policy.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.RemovePolicy.Name">
            <summary>
            <para type="description">
            One or policie names to delete.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.RevokeSecret">
            <summary>
            <para type="synopsis">
            Revoke a secret by its lease ID.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'revoke'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This command revokes a secret by its lease ID that was returned with it.
            Once the key is revoked, it is no longer valid.
            </para><para type="description">
            The related command <c>'Revoke-VltAuthToken'</c> is used to revoke auth tokens.
            </para>
            <para type="link">Revoke-VltSecret</para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeSecret.LeaseId">
            <summary>
            <para type="description">
            The lease ID of a secret to be revoked.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeSecret.PathPrefix">
            <summary>
            <para type="description">
            Revoke all secrets with the matching prefix.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeSecret.Force">
            <summary>
            <para type="description">
            Delete the lease even if the actual revocation operation fails.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.UpdateSecretLease">
            <summary>
            <para type="synopsis">
            Renew the lease on a secret, extending the time that it can
            be used before it is revoked by Vault.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'renew'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Every secret in Vault has a lease associated with it. If the user of
            the secret wants to use it longer than the lease, then it must be
            renewed. Renewing the lease will not change the contents of the secret.
            </para><para type="description">
            To renew a secret, run this command with the lease ID returned when it
            was read. Optionally, request a specific increment in seconds. Vault
            is not required to honor this request.
            </para>
            <para type="link">Update-VltAuthToken</para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.UpdateSecretLease.LeaseId">
            <summary>
            <para type="description">
            The secret lease ID to renew.
            </para><para type="description">
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.UpdateSecretLease.Increment">
            <summary>
            <para type="description">
            The desired increment for the renewal.
            </para><para type="description">
            If not supplied, Vault will use the default TTL. If supplied,
            it may still be ignored. This can be submitted as an integer
            number of seconds or a string duration (e.g. "72h").
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.UpdateSecretLease.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.UpdateAuthToken">
            <summary>
            <para type="synopsis">
            Renew an auth token, extending the amount of time it can be used.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'token-renew'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            You can either specify a specific token ID or indicate to target
            auth token of the client caller.
            </para><para type="description">
            This command is similar to the command <c>'Update-VltSecretLease'</c>
            which is used for renewing secret leases.
            </para><para type="description">
            An optional increment can be given to request a certain number of seconds to
            increment the lease. This request is advisory; Vault may not adhere to it at all.
            </para>
            <para type="link">Update-VltSecretLease</para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.UpdateAuthToken.Token">
            <summary>
            <para type="description">
            The token ID to be renewed.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.UpdateAuthToken.Self">
            <summary>
            <para type="description">
            Specify this switch parameter to indicate the token used by the
            client caller.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.UpdateAuthToken.Increment">
            <summary>
            <para type="description">
            The desired increment for the renewal.
            </para><para type="description">
            If not supplied, Vault will use the default TTL. If supplied,
            it may still be ignored. This can be submitted as an integer
            number of seconds or a string duration (e.g. "72h").
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.RevokeAuthToken">
            <summary>
            <para type="synopsis">
            Revoke one or more auth tokens.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'token-revoke'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This command revokes auth tokens.
            </para><para type="description">
            The related command <c>'Revoke-VltSecret'</c> is used to revoke secrets.
            </para><para type="description">
            By default a token is revoked along with all of its children.
            </para><para type="description">
            With the <c>'-OrphanChildren'</c> switch parameter, only the token will be revoked
            and all of its children will be orphaned.
            </para><para type="description">
            With the <c>'-PathPrefix'</c> parameter, tokens created from the given auth path
            prefix will be deleted, along with all their children. The path cannot specify
            token values or parts of token values.
            </para>
            <para type="link">Revoke-VltSecret</para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeAuthToken.Token">
            <summary>
            <para type="description">
            The token ID to revoke.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeAuthToken.Accessor">
            <summary>
            <para type="description">
            The accessor of the token to revoke.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeAuthToken.Self">
            <summary>
            <para type="description">
            This switch parameter indicates the token of the currently authenticated
            caller should be revoked.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeAuthToken.PathPrefix">
            <summary>
            <para type="description">
            Tokens created from the given auth path prefix will be revoked along
            with all their children.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.RevokeAuthToken.OrphanChildren">
            <summary>
            <para type="description">
            This switch parameter indicates only the specific token will be
            revoked and all of its children will be orphaned.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.SetSecretMountOptions">
            <summary>
            <para type="synopsis">
            Tune configuration options for a mounted secret provider.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'mount-tune'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            </para><para type="description">
            </para>
            </remarks>
            <example>
            <code>
            ##
              Set-VltSecretMountOptions -DefaultLeaseTtl 24h secret
            </code>
            </example>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetSecretMountOptions.MountName">
            <summary>
            <para type="description">
            The name of the mount point to adjust configuration options for.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetSecretMountOptions.DefaultLeaseTtl">
            <summary>
            <para type="description">
            Default lease time-to-live for this backend.
            </para><para type="description">
            If not specified, uses the system default, or the previously set value.
            Set to 'system' to explicitly set it to use the system default.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetSecretMountOptions.MaxLeaseTtl">
            <summary>
            <para type="description">
            Max lease time-to-live for this backend.
            </para><para type="description">
            If not specified, uses the system default, or the previously set value.
            Set to 'system' to explicitly set it to use the system default.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.MountSecretProvider">
            <summary>
            <para type="synopsis">
            Mount a logical secrets provider.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>mount</c> and <c>remount</c> commands.
            </para>
            </summary>
            <remarks>
            <para type="description">
            This command mounts (or remounts) a logical backend for storing and/or
            generating secrets.
            </para><para type="description">
            When remounting, all the secrets from the old path will be revoked, but the
            data associated with the backend(such as configuration), will be preserved.
            </para>
            </remarks>
            <example>
            <para>
            This shows an example of remounting an existing mount path.
            </para><code>
            ##
             
              Mount-VltSecretProvider -OldMountName secret -NewMountName generic
            </code>
            </example>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.Type">
            <summary>
            <para type="description">
            The name of the secrets provider to mount (e.g. generic).
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.MountName">
            <summary>
            <para type="description">
            Mount point for the logical secrets provider.
            </para><para type="description">
            If not specified, this defaults to the name of the type of the mount provider.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.Description">
            <summary>
            <para type="description">
            Human-friendly description of the purpose for the mount.
            This shows up in the list of mounts.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.DefaultLeaseTtl">
            <summary>
            <para type="description">
            Default lease time-to-live for this backend. If not specified,
            uses the global default, or the previously set value. Set to
            '0' to explicitly set it to use the global default.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.MaxLeaseTtl">
            <summary>
            <para type="description">
            Max lease time-to-live for this provider mount. If not specified,
            uses the global default, or the previously set value. Set to '0'
            to explicitly set it to use the global default.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.OldMountName">
            <summary>
            <para type="description">
            The name that identifies an existing mount point of a secrets provider
            to be relocated.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.MountSecretProvider.NewMountName">
            <summary>
            <para type="description">
            The new name to move an existing secrets provider mount.
            </para><para type="description">
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.NewAuth">
            <summary>
            <para type="synopsis">
            Authenticate with Vault against an auth provider using argument
            auth data.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>auth</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            By default, the <c>AuthMethod</c> is assumed to be token.
            If not supplied via the <c>AuthData</c> parameter, a prompt will be issued
            to collect the token ID used to authenticate against the token auth provider.
            </para><para type="description">
            </para>
            <para type="link">Set-VltProfile</para>
            <para type="link">Get-VltProfile</para>
            </remarks>
            <example>
            <para>
            An example of authenticating to the 'userpass' auth provider at the
            default mount point.
            </para><code>
            ##
               
              $creds = Get-Credential ## Interactively and securely prompt for auth creds
              New-VltAuth -AuthMethod userpass -PathData $creds.Username `
                  -AuthData @{ password = $creds.GetNetworkCredential().Password }
            </code>
            </example>
            <example>
            <para>
            An example of authenticating to the <c>okta</c> auth provider at the
            non-default mount point 'okta1'.
            </para><code>
            ##
             
              $creds = Get-Credential ## Interactively and securely prompt for auth creds
              New-VltAuth -AuthMethod okta -MountName okta1 -PathData $creds.Username `
                  -AuthData @{ password = $creds.GetNetworkCredential().Password }
            </code>
            </example>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.AuthMethod">
            <summary>
            <para type="description">
            Selects the authentication method to be used, such as userpass,
            GitHub, or TLS certificates.
            </para><para type="description">
            Each method corresponds to an associated auth provider which defines
            its own set of authentication parameters which are provided via the
            <c>AuthData</c> parameter.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.MountName">
            <summary>
            <para type="description">
            The path at which the auth provider is mounted. If an auth provider is mounted at
            multiple paths, this option can be used to authenticate against a specific path
            associated with a specific provider instance (i.e. with a distinct configuration).
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.PathData">
            <summary>
            <para type="description">
            Defines the sub-path under the mount to authenticate against.
            </para><para type="description">
            By default authentication is targeted against the <c>login</c>
            sub-path under the mount point of an auth provider instance.
            This parameter allows you to define an additional sub-path to
            the default.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.AuthData">
            <summary>
            <para type="description">
            Specifies arbitrary authentication parameters as key-value pairs.
            </para><para type="description">
            Authentication parameters are specific to each authentication
            method, aka auth provider, which define various required or
            optional parameter key names. Refer to the documentation of
            specific auth providers for more details about specific auth
            data key names.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.NoVerify">
            <summary>
            <para type="description">
            Do not verify the token after creation; avoids a use count decrement.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.SaveAsProfile">
            <summary>
            <para type="description">
            Saves the result of the new auth token request to a Vault
            connection profile with the argument name.
            </para><para type="description">
            If the profile name already exists, use the <c>Force</c> switch
            parameter to overwrite it, otherwise an error will be raised
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.NewAuth.Force">
            <summary>
            <para type="description">
            When saving the auth token to a profile with the <c>SaveAsProfile</c>
            parameter, use this flag to overwrite an existing profile with the
            same name, otherwise an error will be raised.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.RemoveData">
            <summary>
            <para type="synopsis">
            Delete data (secrets or configuration) from Vault.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'delete'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Delete sends a delete operation request to the given path.
            </para><para type="description">
            The behavior of the delete is determined by the backend at the given
            path. For example, deleting "aws/policy/ops" will delete the "ops"
            policy for the AWS backend.
            </para><para type="description">
            Use <c>'Get-VltPathHelp'</c> for more details on whether delete is
            supported for a path and what the behavior is.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.RemoveData.Path">
            <summary>
            <para type="description">
            One ore more paths to delete data from.
            </para><para type="description">
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.ReadData">
            <summary>
            <para type="synopsis">
            Read data from Vault.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'read'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Reads data at the given path from Vault. This can be used to read secrets
            and configuration as well as generate dynamic values from materialized
            secret providers. Please reference the documentation for the providers
            in use to determine key structure.
            </para><para type="description">
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.ReadData.Path">
            <summary>
            <para type="description">
            One or more paths to read data from.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.ReadData.WrapTtl">
            <summary>
            <para type="description">
            Indicates that the response should be wrapped in a
            cubbyhole token with the requested TTL.
            </para><para type="description">
            This is a numeric string with an optional suffix "s", "m", or "h";
            if no suffix is specified it will be parsed as seconds.
            </para><para type="description">
            The unwrapped response can be fetched by calling the command
            again but providing the wrapped token ID to the <c>UnwrapToken</c>
            parameter.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.ReadData.UnwrapToken">
            <summary>
            <para type="description">
            One ore more token ID representing wrapped data returned by a
            prior call of this command with the <c>WrappTtl</c> parameter
            set.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.ReadData.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetPathHelp">
            <summary>
            <para type="synopsis">
            Look up the help for a path.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>path-help</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            All endpoints in Vault from system paths, secret paths, and credential
            providers provide built-in help.
            This command looks up and outputs that help.
            </para><para type="description">
            The command requires that the vault be unsealed, because otherwise
            the mount points of the backends are unknown.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetPathHelp.Path">
            <summary>
            <para type="description">
            One or more paths to get help for.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetDataList">
            <summary>
            <para type="synopsis">
            List data from Vault.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>list</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Retrieve a listing of available data.
            The data returned, if any, is provider- and endpoint-specific.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetDataList.Path">
            <summary>
            <para type="description">
            One or more paths for which to list data.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetDataList.WrapTtl">
            <summary>
            <para type="description">
            Indicates that the response should be wrapped in a
            cubbyhole token with the requested TTL.
            </para><para type="description">
            This is a numeric string with an optional suffix "s", "m", or "h";
            if no suffix is specified it will be parsed as seconds.
            </para><para type="description">
            The unwrapped response can be fetched by calling the command
            again but providing the wrapped token ID to the <c>UnwrapToken</c>
            parameter.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetDataList.UnwrapToken">
            <summary>
            <para type="description">
            One ore more token ID representing wrapped data returned by a
            prior call of this command with the <c>WrappTtl</c> parameter
            set.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetDataList.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.LockServer">
            <summary>
            <para type="synopsis">
            Seal the vault.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'seal'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Sealing a vault tells the Vault server to stop responding to any
            access operations until it is unsealed again. A sealed vault throws away
            its master key to unlock the data, so it is physically blocked from
            responding to operations again until the vault is unsealed with
            the "unseal" command or via the API.
            </para><para type="description">
            This command is idempotent, if the vault is already sealed it does nothing.
            </para><para type="description">
            If an unseal has started, sealing the vault will reset the unsealing
            process. You'll have to re-enter every portion of the master key again.
            </para>
            <para type="link">Unlock-VltServer</para>
            </remarks>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetProfile">
            <summary>
            <para type="synopsis">
            Retrieves the list of Vault connection profiles defined for the
            current user/ or the details of a specific Vault connection profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetProfile.VaultProfile">
            <summary>
            <para type="description">
            The name of one or more profiles for which to return the details.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.GetProfile.ShowLabels">
            <summary>
            <para type="description">
            If this switch is specified, labels will be included in the result list.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.SetProfile">
            <summary>
            <para type="synopsis">
            Defines or updates a Vault connection profile.
            </para>
            </summary>
            <remarks>
            <para type="description">
            A connection profile is a named and persisted collection of
            Vault connection attributes, which may include the Vault endpoint
            URL address and a Vault authentication token.
            </para><para type="description">
            Most of the Vault commands (all the ones that interact directly with
            the Vault server) take an optional parameter <c>'-VaultProfile'</c>
            (or the alias <c>'-vp'</c>) to reference a named profile for the current
            user. Additionally, any attributes defined in the profile may be
            individually overridden when being called upon.
            </para><para type="description">
            Beside explicitily defining a profile with this command, you can also
            save a profile as the result of a new authentication via the
            <c>'New-VltAuth'</c> command.
            </para>
            <para type="link">Get-VltProfile</para>
            <para type="link">New-VltAuth</para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.SaveAs">
            <summary>
            <para type="description">
            Specifies the name under which to save the profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.VaultAddress">
            <summary>
            <para type="description">
            Specify the Vault endpoint URL address to include in the profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.VaultToken">
            <summary>
            <para type="description">
            Specify the Vault authentication token to include in the profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.Label">
            <summary>
            <para type="description">
            Provides an optional human-friendly descriptive name to the profile
            for quick and easy recognition upon inspection.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.VaultProfile">
            <summary>
            <para type="description">
            Reference an existing profile whose attributes will be copied
            over unless overridden by other parameters.
            </para><para type="description">
            If no overrides are specified, this will create a copy of the
            existing profile being referenced.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.Force">
            <summary>
            <para type="description">
            This switch parameter must be specified whenever referencing
            a profile name that already exists. Without it, en error will
            be raised.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetProfile.Remove">
            <summary>
            <para type="description">
            This switch parameter is used to remove an existing profile.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.UnlockServer">
            <summary>
            <para type="synopsis">
            Unseal the vault by entering a portion of the master key.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'unseal'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            Once all portions are entered, the vault will be unsealed.
            </para><para type="description">
            Every Vault server initially starts as sealed. It cannot perform any
            operation except unsealing until it is unsealed. Secrets cannot be accessed
            in any way until the vault is unsealed. This command allows you to enter
            a portion of the master key to unseal the vault.
            </para><para type="description">
            In order to abort the unsealing process and discard any prior keys
            that have already been entered in the process, use the
            <c>'Lock-VltServer'</c> command.
            </para>
            <para type="link">Lock-VltServer</para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.UnlockServer.Key">
            <summary>
            <para type="description">
            One or more unseal keys to apply to the unseal process.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.Global">
            <summary>
            Defines common constants and utility routines.
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.VaultBaseCmdlet">
            <summary>
            Base class for most cmdlets that interact with the Vault server.
            </summary>
            <remarks>
            This base class defines a common set of base parameters such as specifying
            connection details and commonly used methods.
            </remarks>
        </member>
        <member name="F:Zyborg.Vault.POSH.VaultBaseCmdlet._client">
            <summary>
            Caches the result of the most recent invocation to <see cref="M:Zyborg.Vault.POSH.VaultBaseCmdlet.ResolveVaultClient"/>.
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultBaseCmdlet.VaultSession">
            <summary>
            <para type="description">
            Specifies a Vault Session object that represents a connected-state
            container to a Vault server.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultBaseCmdlet.VaultProfile">
            <summary>
            <para type="description">
            Specifies the name of a persisted Vault connection profile whose
            attributes define default parameters for connecting to a Vault
            server endpoint.
            </para><para type="description">
            Other connection parameters on this command may override whatever
            attributes are defined in the profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultBaseCmdlet.VaultAddress">
            <summary>
            <para type="description">
            Specifies the Vault server connection endpoint URL.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultBaseCmdlet.VaultToken">
            <summary>
            <para type="description">
            Specifies the Vault server connection authentication token
            to identify the caller to the server.
            </para>
            </summary>
        </member>
        <member name="M:Zyborg.Vault.POSH.VaultBaseCmdlet.ResolveVaultClient">
            <summary>
            Resolves a Vault Client instance based on the common parameters passed into
            this cmdlet instance, the current environment (variables), and the context
            of the invocation, such as user-specific Vault CLI cache and configuration
            files, and PowerShell configuration, such as profiles.
            </summary>
            <returns></returns>
        </member>
        <member name="T:Zyborg.Vault.POSH.GetStatus">
            <summary>
            <para type="synopsis">
            Outputs the state of the Vault, sealed or unsealed and if HA is enabled.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>status</c> command.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.VaultProfile">
            <summary>
            <para type="description">
            Defines the elements of a Vault connection profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultProfile.Label">
            <summary>
            <para type="description">
            An optional human-friendly label for the profile.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultProfile.VaultAddress">
            <summary>
            <para type="description">
            A URL for the Vault server endpoint.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultProfile.VaultToken">
            <summary>
            <para type="description">
            An authentication token to be used to identify the caller
            when interacting with the Vault server.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.VaultSession">
            <summary>
            <para type="description">
            Local state for interacting with a Vault server endpoint.
            </para>
            </summary>
        </member>
        <member name="M:Zyborg.Vault.POSH.VaultSession.#ctor(System.String,System.String)">
            <summary>
            Creates a session with the two minimum, necessary components
            provided as parameters.
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultSession.VaultAddress">
            <summary>
            URL specifying the Vault server endpoint.
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.VaultSession.VaultToken">
            <summary>
            The authentication Token to self-identify with to the Vault server.
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.SetPolicy">
            <summary>
            <para type="synopsis">
            Create or update a policy with the given rules.
            </para><para type="synopsis">
            Comparable to the vault CLI <c>'policy-write'</c> command.
            </para>
            </summary>
            <remarks>
            <para type="description">
            If updating an existing policy, the entire contents of the
            existing policy rules definitions will be replaced.
            </para><para type="description">
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetPolicy.Name">
            <summary>
            <para type="description">
            The name of the policy to create or update.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.SetPolicy.Rules">
            <summary>
            <para type="description">
            The rules content to write to the policy definition.
            </para>
            </summary>
        </member>
        <member name="T:Zyborg.Vault.POSH.WriteData">
            <summary>
            <para type="synopsis">
            Write data (secrets or configuration) into Vault to a backend provider
            logically mounted at a specified path.
            </para>
            </summary>
            <remarks>
            <para type="description">
            There are 3 different Parameter Sets corresponding to 3 typical usages of
            this cmdlet.
            </para><para type="description">
            In the first (default) usage, a single vault path is specified
            and one or more key-value pairs are provided. The Keys are all provided as
            an array, and the values are all provided as an array, and the length of
            these two arrays must be equal. Additionally, the Keys and Values can be
            provided from the pipeline using objects with the corresponding property
            names.
            </para><para type="description">
            In the second and third usages, either a single map of key-values is provided
            or no values are provided at all using the <c>-NoValues</c> switch (some
            vault backends support writing no value to trigger an action or behavior).
            Multiple vault paths are specified into which all will receive the same set
            of data values. Tha Paths can be provided from the pipeline.
            </para>
            </remarks>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.Path">
            <summary>
            <para type="description">
            The path to which to write one or more key-value pairs of secrets.
            This parameter set allows you to write multiple key-values to a single path.
            </para><para type="description">
            The behavior of the write is determined by the secret provider mounted
            at the given path. For example, writing to "aws/policy/ops" will create
            an "ops" IAM policy for the AWS secret provider (configuration), but
            writing to "consul/foo" will write ta value directly into Consul at that
            key.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.Key">
            <summary>
            <para type="description">
            Specifies one or more keys to set a value for.
            </para><para type="description">
            The count of corresponding values specified with the <c>Value</c>
            parameter must match the count of keys.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.Value">
            <summary>
            <para type="description">
            Specifies one or more secret values to set for the corresponding keys.
            </para><para type="description">
            The count of corresponding keys specified with the <c>Key</c> parameter
            must match the count of values.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.Paths">
            <summary>
            <para type="description">
            The paths to which to write one ore more key-value pairs.
            This parameter set allows you to write to multiple paths simultaneously.
            </para><para type="description">
            The behavior of the write is determined by the secret provider mounted
            at the given path. For example, writing to "aws/policy/ops" will create
            an "ops" IAM policy for the AWS secret provider (configuration), but
            writing to "consul/foo" will write ta value directly into Consul at that
            key.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.Data">
            <summary>
            <para type="description">
            A map of key-value pairs to write to the target path or paths.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.NoValues">
            <summary>
            <para type="description">
            Forces the write to without any data values specified. This allows writing
            to keys that do not need or expect any fields to be specified.
            </para>
            </summary>
        </member>
        <member name="P:Zyborg.Vault.POSH.WriteData.KeepSecretWrapper">
            <summary>
            <para type="description">
            When specified, the returned result maintains the meta data wrapper
            for the secret result.
            </para>
            </summary>
        </member>
    </members>
</doc>