Skip to content
Ansible Galaxy Collection of playbooks, roles, and plugins to manage Github tasks.
Python
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/workflows
molecule/default
plugins/lookup
.flake8
.gitignore
.pre-commit-config.yaml
.yamllint
LICENSE
Pipfile
Pipfile.lock
README.md
galaxy.yml
pyproject.toml

README.md

github_version

Build Status GitHub GitHub release (latest SemVer) GitHub followers Twitter Follow

You can find this collection on Ansible Galaxy here.

Usage

Install this collection locally:

ansible-galaxy collection install artis3n.github

This installs to the first location in your ANSIBLE_COLLECTIONS_PATHS, which by default is ~/.ansible/collections. You can modify the installation path with -p:

ansible-galaxy collection install artis3n.github -p collections/

Then you can use the lookup plugin in your playbooks. Note that, unlike roles and modules imported via a collection, plugins seem to always require their full name.

collections:
  - artis3n.github
tasks:
  - name: Ansible | Get latest release
    set_fact:
      ansible_version: "{{ lookup('artis3.github.latest_release', 'ansible/ansible')[1:] }}

Note: [1:] is used to strip out the v in the version tag, e.g. v1.1.0 becomes 1.1.0.

Contents

This collection includes the following items related to interacting with GitHub:

Plugins

Lookup plugins

latest_release

This lookup plugin retrieves the latest tagged release version of a public Github repository.

A future version will support a Github token as an environment variable to work against private repositories.

Example:

tasks:
  - name: Ansible | Get latest release
    set_fact:
      ansible_version: "{{ lookup('artis3.github.latest_release', 'ansible/ansible')[1:] }}

Here's a longer example to demonstrate the benefit of this plugin to download the latest released Terraform version by validating its checksum:
- name: Terraform | Get latest release
  set_fact:
    terraform_version: "{{ lookup('artis3.github.release_version', 'hashicorp/terraform')[1:] }}"

- name: Terraform | Ensure directory
  file:
    path: "{{ install_dir }}/terraform_{{ terraform_version }}"
    state: directory
  register: terraform_directory

- name: Terraform | Get hashes
  get_url:
    url: https://releases.hashicorp.com/terraform/{{ terraform_version }}/terraform_{{ terraform_version }}_SHA256SUMS
    dest: "{{ terraform_directory.path }}/SHA256SUMS"
  register: terraform_shas_file
  changed_when: false

- name: Terraform | Construct regex
  set_fact:
    terraform_sha_hash: "{{ '.*\\s\\sterraform_' + (terraform_version | regex_escape()) + '_linux_amd64\\.zip' }}"

- name: Terraform | Extract sha hash
  set_fact:
    # https://regex101.com/r/RS94Us/1
    terraform_sha_string: "{{ lookup('file', terraform_shas_file.dest) | regex_findall(terraform_sha_hash) | first }}"

- name: Terraform | Download
  get_url:
    url: https://releases.hashicorp.com/terraform/{{ terraform_version }}/terraform_{{ terraform_version }}_{{ os_short }}.zip
    dest: "{{ install_dir }}/terraform_{{ terraform_version }}.zip"
    checksum: sha256:{{ terraform_sha_string.split(' ')[0] }}
  register: terraform_download

Development

Ansible has very strict expectations for where to look for a collection. There are open issues against Ansible to change this behavior to make local testing easier. However for the time being, you must do the following.

You can modify the ANSIBLE_COLLECTIONS_PATHS environment variable to add custom paths for Ansible to search for collections, however collections must be in the following format at the directory location specified in ANSIBLE_COLLECTIONS_PATHS:

collection/
├── ansible_collections/
│   ├── <namespace, e.g. artis3n>/
│   │   ├── <collection name, e.g. github>/
|   |   |   ├── plugins/
|   |   |   |   ├── lookup/
|   |   |   |   |   └── .../
|   |   |   └── .../

So, you must clone this repository to a location under collection/ansible_collections/ and modify ANSIBLE_COLLECTIONS_PATHS to include that absolute path in order for molecule test to find this collection.

You will notice that in molecule/default/molecule.yml I hard-code my personal directory in order to easily run molecule tests:

ANSIBLE_COLLECTIONS_PATHS: "~/.ansible/collections:~/Nextcloud/Development/collections"

I don't have a good way of writing something in code that can apply more generally due to the way Ansible currently handles collections so you'll likely need to override that to test this locally.

Alternatively, you can submit a draft pull request to this repository and a GitHub Actions workflow will trigger and run molecule test on your pull request.

TODO

  • Tests 😬
  • Support Github tokens for private repository lookups

Contributing

This repository welcomes contributions. Please fork this repository and file a pull request to the master branch. Your changes must include any appropriate tests under the molecule/ directory. Read about how to use Molecule from the official documentation here and from Jeff Geerling here.

Publishing a new version

This repository uses Github Actions to build and publish new releases to Ansible Galaxy. The action in question can be found on the GitHub Marketplace.

You can’t perform that action at this time.