You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current usage workflow connects via winrm to a remote windows to setup hyperv.
In my use case I deploy terraform in the hyper-v system, and connect via 127.0.0.1
However GPO create problems because the winrm modules used in this project require basic authentication and they do not offer ntlm cyphering.
One alternative is having another communication channel: offer ssh in addition to winrm.
The other alternative, and the one suggested here, create a flag "local = true" in the hyperv config settings to execute all the powershell commands in the same host running terraform. In this scenario username, password, host, etc... will not be used....
Powershell commands would be executed with the same credentials of terraform.
This will avoid all kind of communication errors, and if I want to use this pluging in a remote system... I deploy in this system terraform+plugin, connect via ssh, and execute everthing in local mode.
The text was updated successfully, but these errors were encountered:
ghost
changed the title
Allow "local" mode
Create "local" mode
May 2, 2021
@malikumaliku not sure what you mean by "nltm cyphering". The provider supports basic, ntlm and with the new release kerberos.
I have done a bit of refactoring that should make this easier to implement, so I am going to leave this feature request open (and time permitting give it a go)
taliesins
changed the title
Create "local" mode
[FeatureRequest] Create "local" mode
Apr 17, 2022
The current usage workflow connects via winrm to a remote windows to setup hyperv.
In my use case I deploy terraform in the hyper-v system, and connect via 127.0.0.1
However GPO create problems because the winrm modules used in this project require basic authentication and they do not offer ntlm cyphering.
One alternative is having another communication channel: offer ssh in addition to winrm.
The other alternative, and the one suggested here, create a flag "local = true" in the hyperv config settings to execute all the powershell commands in the same host running terraform. In this scenario username, password, host, etc... will not be used....
Powershell commands would be executed with the same credentials of terraform.
This will avoid all kind of communication errors, and if I want to use this pluging in a remote system... I deploy in this system terraform+plugin, connect via ssh, and execute everthing in local mode.
The text was updated successfully, but these errors were encountered: