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
{{ message }}
This repository has been archived by the owner on Oct 30, 2018. It is now read-only.
Hi, This is because win_environment is not available in Ansible 1.9.3. As the docs state 'New in version 2.0.'
You can probably run it by grabbing the win_environment.ps1 file into your ansible configuration's library folder (i.e. if you ansible configuration is in /etc/ansible/ then put the file in /etc/ansible/library
I would be interested to know if you can use 'PATH=%PATH%;C:\selenium' in the value: as I don't recall testing the module using that syntax. If it fails you could fetch the current environment value for path with a script or perhaps replace the entire PATH value with a literal string (depending on what you are trying to achieve this could be a dangerous or desirable thing to do though).
@anthonygreen -- as noted by @jhawkesworth, this is due to win_environment being new in 2.0. If you have a moment to answer his question above, though, that would be helpful!
Otherwise -- if we don't hear from you in a week or two, we'll go ahead and close this.
Issue Type:
Bug Report
Ansible Version:
1.9.3
Ansible Configuration
Docker.py version
1.2.3
Environment
Running from: OS X 10.9.5
Managing: Windows 10
Summary:
the win_environment module is not available to ansible
Steps to reproduce
This playbook fails
with the error
The text was updated successfully, but these errors were encountered: