community.general.appimage module – Manage AppImage packages
Note
This module is part of the community.general collection (version 14.0.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.general.
To use it in a playbook, specify: community.general.appimage.
New in community.general 13.4.0
Synopsis
Install, update, and remove applications distributed as AppImage files.
The module installs AppImage files into a user-controlled directory.
Sources can be local AppImage files, direct AppImage URLs, GitHub release pages containing AppImage assets, or https://appimage.github.io catalog entries.
Parameters
Parameter |
Comments |
|---|---|
Glob pattern used to select the AppImage asset from a GitHub release. If the pattern matches multiple assets, the module fails and asks for a more specific pattern. Default: |
|
The attributes the resulting filesystem object should have. To get supported flags look at the man page for This string should contain the attributes in the same order as the one displayed by The |
|
URL of the https://appimage.github.io-compatible JSON feed used when Default: |
|
GitHub token used when querying GitHub releases. This can be useful for private repositories or higher API rate limits. |
|
Name of the group that should own the filesystem object, as would be fed to When left unspecified, it uses the current group of the current user unless you are root, in which case it can preserve the previous ownership. Specifying a numeric group name (for example, “1000”) will be assumed to be a group ID (GID) and not a group name. To prevent confusion, avoid using purely numeric group names. |
|
Directory where the AppImage executable is installed. Default: |
|
The permissions the resulting filesystem object should have. For those used to Giving Ansible a number without following either of these rules will end up with a decimal number which will have unexpected results. As of Ansible 1.8, the mode may be specified as a symbolic mode (for example, If If Specifying |
|
Name of the managed AppImage. This is used as the installed executable filename. When |
|
Name of the user that should own the filesystem object, as would be fed to When left unspecified, it uses the current user unless you are root, in which case it can preserve the previous ownership. Specifying a numeric username (for example, “1000”) will be assumed to be a user ID (UID) and not a username. To prevent confusion, avoid using purely numeric usernames. |
|
The level part of the SELinux filesystem object context. This is the MLS/MCS attribute, sometimes known as the When set to |
|
The role part of the SELinux filesystem object context. When set to |
|
The type part of the SELinux filesystem object context. When set to |
|
The user part of the SELinux filesystem object context. By default it uses the When set to |
|
Desired state of the AppImage. When When
Choices:
|
|
Timeout in seconds for HTTP requests. Default: |
|
Influence when to use atomic operation to prevent data corruption or inconsistent reads from the target filesystem object. By default this module uses atomic operations to prevent data corruption or inconsistent reads from the target filesystem objects, but sometimes systems are configured or just broken in ways that prevent this. One example is docker mounted filesystem objects, which cannot be updated atomically from inside the container and can only be written in an unsafe manner. This option allows Ansible to fall back to unsafe methods of updating filesystem objects when atomic operations fail (however, it doesn’t force Ansible to perform unsafe writes). IMPORTANT! Unsafe writes are subject to race conditions and can lead to data corruption. Choices:
|
|
Source used to obtain the AppImage. This can point directly to an AppImage URL, a local AppImage file path, a When omitted with |
|
If Choices:
|
|
GitHub release tag to install when This can only be used with sources that provide release versions, such as GitHub releases pages. By default, GitHub release pages use the latest release. |
Attributes
Attribute |
Support |
Description |
|---|---|---|
Support: full |
Can run in |
|
Support: none |
Returns details on what has changed (or possibly needs changing in |
Examples
- name: Install an AppImage from a direct URL
community.general.appimage:
name: example
url: https://example.com/downloads/example-x86_64.AppImage
- name: Install an AppImage from a local file
community.general.appimage:
name: example
url: /tmp/example-x86_64.AppImage
- name: Install an AppImage from the appimage.github.io catalog
community.general.appimage:
name: appimagetool
- name: Install the latest x86_64 AppImage from GitHub releases
community.general.appimage:
name: example
url: https://github.com/example/example/releases
state: latest
asset_name: "*x86_64.AppImage"
- name: Install a specific GitHub release tag
community.general.appimage:
name: example
url: https://github.com/example/example/releases
version: v1.2.3
- name: Remove an AppImage
community.general.appimage:
name: example
state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
Key |
Description |
|---|---|
AppImage catalog entry name used to resolve the source. Returned: when installing from the appimage.github.io catalog Sample: |
|
AppImage catalog page used to resolve the source. Returned: when installing from the appimage.github.io catalog Sample: |
|
Path to the managed AppImage executable. Returned: always Sample: |
|
Local AppImage source path. Returned: when installing from a local path or Sample: |
|
Resolved AppImage download URL. Returned: when Sample: |
|
GitHub release tag that was installed. Returned: when installing from a GitHub release Sample: |