Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

common-ansible

🖥️▶️ Shared Ansible files that propagate to downstream projects (including boilerplate code for new projects)
https://github.com/ProfessorManhattan/common-ansible

Last synced: 5 days ago
JSON representation

  • Table of Contents

  • Overview

    • Megabyte Labs - system inherit many of their files (e.g. configuration files) from a cascade of [common file repositories](https://gitlab.com/megabyte-labs/common). Each repository includes a bundle of shared files as a submodule. The submodule is located in the `.common/` folder in the root of each project. The submodule links to the common file repository that corresponds to the type of project (e.g. Ansible projects link their `.common/` folder to the [Ansible common files repository](https://gitlab.com/megabyte-labs/common/ansible)). Each of the common file repositories houses all the data that is required for a downstream repository but many of the files in the common file repository are actually inherited from a repository even further upstream.
    • Megabyte Labs - system inherit many of their files (e.g. configuration files) from a cascade of [common file repositories](https://gitlab.com/megabyte-labs/common). Each repository includes a bundle of shared files as a submodule. The submodule is located in the `.common/` folder in the root of each project. The submodule links to the common file repository that corresponds to the type of project (e.g. Ansible projects link their `.common/` folder to the [Ansible common files repository](https://gitlab.com/megabyte-labs/common/ansible)). Each of the common file repositories houses all the data that is required for a downstream repository but many of the files in the common file repository are actually inherited from a repository even further upstream.

  • Documentation Partials and Variable Inheritence

  • Common File Propagation Process

  • Common File Sub-Types

    • Ansible common file repository - role`, and `files-playbook`. In this case, during the project update process, the `files` are copied into both the `files-role` and `files-playbook` folders. The `files-role` and `files-playbook` folders contain files meant for all Ansible projects but files intended for their sub-types. In this case, the sub-types are `role` and `playbook` - two different types of Ansible projects that require slightly different sets of files.
    • Megabyte Labs GitLab group - groups will be:
    • ansible-molecule
    • app
    • ci-pipeline
    • software
    • Megabyte Labs GitLab group - groups will be:
    • ansible-molecule
    • app
    • ci-pipeline
    • software
    • Ansible common file repository - role`, and `files-playbook`. In this case, during the project update process, the `files` are copied into both the `files-role` and `files-playbook` folders. The `files-role` and `files-playbook` folders contain files meant for all Ansible projects but files intended for their sub-types. In this case, the sub-types are `role` and `playbook` - two different types of Ansible projects that require slightly different sets of files.

  • Templated Files

Categories
Common File Sub-Types 12 Common File Propagation Process 9 Templated Files 3 Overview 2 Documentation Partials and Variable Inheritence 2 Table of Contents 1
Sub Categories
Keywords
mblabs 2 megabytelabs 2 washingtondc 2 npm 2 package 2 professormanhattan 2 common 1 configurations 1 files 1 gitlab-ci 1 shared 1 taskfiles 1 ansible 1 awesome 1 boilerplate 1 playbook 1 role 1 samples 1