Matt, Thanks for the response. I've actually done some more work on this and got a workaround.
On Thu, 8 Sep 2016, at 05:01 PM, Matt Davis wrote: > Hard to say without taking apart the Azure cmdlets, but I'd suspect they're > internally trying to use a Windows credential cache, which has always been a > no-go for me under a WinRM session (though IIRC it fails loudly when you > try). > Looking at the source for Get-AzureRMBackupVaultCredential (https://github.com/Azure/azure-powershell/blob/dev/src/ResourceManager/AzureBackup/Commands.AzureBackup/Cmdlets/VaultCredentials/GetAzureRMBackupVaultCredentials.cs) I came to the conclusion that it was probably an issue with hitting one of the X509 api calls. > Some of the stuff that will likely land in Ansible 2.3 may help (become > support, various other tricks for escaping WinRM's restrictions), but not > sure what to tell you meantime. I ended up modifying the script to run the cmdlets in a scheduled job (roughly based on the code in this issue https://github.com/ansible/ansible-modules-extras/issues/287). Is support for "various other tricks" likely to include help for running awkward tasks as scheduled? > Maybe ask the Azure folks why their cmdlets don't work under WinRM... Yeah, I 'll try opening an issue. Thanks again for your help. Regards, Barney. -- Barney Sowood [email protected] -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1473412435.1728449.720490617.2528D010%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
