Closed haerdib closed 3 years ago
@brenzi the current provision call needs an urllist file input (according to #1). But I guess the standard use case will be to use the keyvault_pool.txt
default file which is generated by thekeyvault list
command. Would it be a possibility to make the <urllist>
input of the provision call optional? If it is not given, the default filepath will be taken.
@brenzi the current provision call needs an urllist file input (according to #1). But I guess the standard use case will be to use the
keyvault_pool.txt
default file which is generated by thekeyvault list
command. Would it be a possibility to make the<urllist>
input of the provision call optional? If it is not given, the default filepath will be taken.
the idea is that the user can select a subset of keyvaults. There may be many more than necessary
adds all keyvault interaction implementation, though not yet finished. Unfinished tasks are marked with a TODO within the code (mostly because these should be done within a different issue, respective task is on hold / stalled due to pending PR)
The following tasks are still on TODO: