palazzem / ansible-portable Goto Github PK

Overview

Project builder depends on a specific Ansible version. We should make it generic so that:

• The builder workflow can run daily, picking the latest available version
• No references in the README about what version to use (remove the version number)

Overview

Update Ansible portable following the update instructions. When doing that, we should verify:

• If https://github.com/palazzem/hanzo bootstrap script works
• If https://github.com/palazzem/hanzo YAML configuration works between Ansible 2.9 and 4+

Overview

This project uses ansible==7.3.0 which includes all the community packages. We should strip it down to use just ansible-core and let projects using it to download extra collections.

The downside of not doing the change, is that the package is 229 MB as shown here: https://github.com/palazzem/ansible-portable/releases/tag/7.3.0

Overview

builder action builds the package but nobody verifies if it works or not. We should run a separate job that executes the following commands:

# Extracts Ansible in ansible-2.14.3/ folder and runs a test command
$ tar -xf ansible-2.14.3.tar.gz
$ PYTHONPATH=ansible-2.14.3 python ansible-2.14.3/ansible adhoc localhost -m ping

This command is an example and replicates what is written in the README.md at the time of writing.

Overview

GitHub Actions are building the container but the resulting package is discarded. We should store the package as artifact so that it can be downloaded from the packages section without creating a GitHub release every time.

This script should run weekly, and we can safely discard packages after 30 days.