Skip to content

mto79/ansible_collection_mto79.ansible

Repository files navigation

Ansible collection - mto79.ansible

MTO79 Ansible collection for installing and configuring Ansible on system.

Table of Contents

Name Minimum Version
ansible 2.11.0
ansible-lint 5.1.3
jinja2 2.11.3
ansible.posix 1.0.0
Plugin Description Tests
Module Description Tests
Role Description Tests
proxyservices.ansible.navigator Ansible role for installing ansible navigator.

Usage:

export NEW_ROLE_NAME="new_role"
./add-role.sh ${NEW_ROLE_NAME}
# Or run the script and it will prompt you for the name

Install pre-commit

pip install pre-commit

Set hooks in .pre-commit-config.yaml

repos:
- repo: https://github.com/ansible/ansible-lint.git
  rev: v4.2.0
  hooks:
    - id: ansible-lint
      files: \.(yaml|yml)$

Enable pre-commit for your git repository

$ pre-commit install
pre-commit installed at .git/hooks/pre-commit

Testing pre-commit

pre-commit run --all-files
Ansible-lint.............................................................Passed

or just type:

git commit

This collection follows Semantic Versioning. More details on versioning can be found in the Ansible docs.

We plan to regularly release new minor or bugfix versions once new features or bugfixes have been implemented.

Releasing the current major version happens from the devel branch.

Generating changelogs

Install antsibull-changelog:

pip install antsibull-changelog

Initialize changelogs for your repository

antsibull-changelog init <path/to/your/collection>

Validate your changelog fragments

antsibull-changelog lint

Generate the changelog for your release

Create an entry of changelog in changelogs/changelog.yaml

Run antsibull-changelog release command (install antsibull tool before)

antsibull-changelog release --update-existing --version 1.0.0

Check changelogs/changelog.yaml file and generated changelog in CHANGELOG.rst and fix if need

Change version in galaxy.yaml file to the new one.

Commit and merge changes in changelog or/and docs

Git tag <version_tag> where <version_tag> is tag of the new version - for example 2.3.4 Push tags to upstream - git push upstream <version_tag>

wait until check and release jobs finish and check in galaxy that new version is uploaded: https://galaxy.ansible.com/containers/podman

Release notes

See CHANGELOG.rst.

See LICENSE.

About

MTO79 - Ansible Collection - Ansible

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages