Andrew Savinykh
Andrew Savinykh
It prints the following: ``` 2018-12-11 16:14:07 TRACE [warp_runner] self_path="C:\\Users\\asavinykh\\test.exe" 2018-12-11 16:14:07 TRACE [warp_runner] self_file_name="test.exe" 2018-12-11 16:14:07 TRACE [warp_runner] cache_path="C:\\Users\\asavinykh\\AppData\\Local\\warp\\packages\\test.exe" 2018-12-11 16:14:07 TRACE [warp_runner] target_exec="E:\\Sources\\DevOps\\HelperApps\\OctoVars\\bin\\Debug\\netcoreapp2.1\\win10-x64\\publish\\OctoVars.exe" 2018-12-11 16:14:07 TRACE [warp_runner] target_path="E:\\Sources\\DevOps\\HelperApps\\OctoVars\\bin\\Debug\\netcoreapp2.1\\win10-x64\\publish\\OctoVars.exe"...
@dgiagio yep, that worked, thanks. Do you think it's worth fixing in code?
Unrelated to the issue question, am I guessing right, that if a program is looking for it's config file in the executable folder, it's unlikely to find it because the...
Another use case to support is using WinRm and SSH connection in the same playbook / template. Currently both SSH and Winrm credentials represent with the same "Machine" type which...
@tallpauley `vault write secret/passwords .vault-ui-plugin=password-manager` may not fly if whatever is already working with a secret does not expect this additional field and can potentially break because of it. This...
@msessa the use case is straight forward - to be able to read and to write to the cubbyhole backend. >At this time, cubbyhole is only used internally by vault...
>I am unable to reproduce this issue, I've used the policy that you provided in the issue description and browsed to http://vault-ui/secrets/generic/secret/some/path/ and I'm able to create a new secret,...
No worries. Thank you for your time ;) I personally do not require any ETA, I just know that you guys appreciate feedback and improvements suggestions, so I'm doing my...
@msessa feel free to edit the subject of the issue to reflect what's going on more precisely. If you as a collaborator do not have access to edit the issue...
VMWare own powercli retreive VMs by name regardless of case, e.g. both `Get-VM name` and `Get-VM NAME` work. I would expect the same from the vmware modules.