community.windows.win_psmodule module – Adds or removes a Windows PowerShell module
Note
This module is part of the community.windows collection (version 1.13.0).
You might already have this collection installed if you are using the ansible
package.
It is not included in ansible-core
.
To check whether it is installed, run ansible-galaxy collection list
.
To install it, use: ansible-galaxy collection install community.windows
.
To use it in a playbook, specify: community.windows.win_psmodule
.
Synopsis
This module helps to install Windows PowerShell modules and register custom modules repository on Windows-based systems.
Parameters
Parameter |
Comments |
---|---|
Accepts the module’s license. Required for modules that require license acceptance, since interactively answering the prompt is not possible. Corresponds to the Installation of a module or a dependency that requires license acceptance cannot be detected in check mode, but will cause a failure at runtime unless accept_license=true. Choices:
|
|
If Choices:
|
|
If It doesn’t work with the parameters It doesn’t work with the Choices:
|
|
Overrides warning messages about module installation conflicts If there is an existing module with the same name and version, force overwrites that version Corresponds to the If module as dependency, it will also force reinstallation of dependency. Updating them to latest if version isn’t specified in module manifest. Choices:
|
|
The maximum version of the PowerShell module that has to be installed. |
|
The minimum version of the PowerShell module that has to be installed. |
|
Name of the Windows PowerShell module that has to be installed. |
|
Password to authenticate against private repository. |
|
Name of the custom repository to use. |
|
The exact version of the PowerShell module that has to be installed. |
|
If Choices:
|
|
If If If Choices:
|
|
URL of the custom repository to register. DEPRECATED, will be removed in a major release after |
|
Username to authenticate against private repository. |
Notes
Note
PowerShell modules needed - PowerShellGet >= 1.6.0 - PackageManagement >= 1.1.7
PowerShell package provider needed - NuGet >= 2.8.5.201
On PowerShell 5.x required modules and a package provider will be updated under the first run of the win_psmodule module.
On PowerShell 3.x and 4.x you have to install them before using the win_psmodule.
See Also
See also
- community.windows.win_psrepository
The official documentation on the community.windows.win_psrepository module.
Examples
---
- name: Add a PowerShell module
community.windows.win_psmodule:
name: PowerShellModule
state: present
- name: Add an exact version of PowerShell module
community.windows.win_psmodule:
name: PowerShellModule
required_version: "4.0.2"
state: present
- name: Install or update an existing PowerShell module to the newest version
community.windows.win_psmodule:
name: PowerShellModule
state: latest
- name: Install newer version of built-in Windows module
community.windows.win_psmodule:
name: Pester
skip_publisher_check: yes
state: present
- name: Add a PowerShell module and register a repository
community.windows.win_psmodule:
name: MyCustomModule
repository: MyRepository
state: present
- name: Add a PowerShell module from a specific repository
community.windows.win_psmodule:
name: PowerShellModule
repository: MyRepository
state: present
- name: Add a PowerShell module from a specific repository with credentials
win_psmodule:
name: PowerShellModule
repository: MyRepository
username: repo_username
password: repo_password
state: present
- name: Remove a PowerShell module
community.windows.win_psmodule:
name: PowerShellModule
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
---|---|
True when Nuget package provider is installed. Returned: always Sample: |
|
A message describing the task result. Returned: always Sample: |
|
True when a custom repository is installed or removed. Returned: always Sample: |