58b393322b
This patch set fixes a recent issue that was introducing following a refactor Pegleg table output. The related CLI unit tests were changed to stop checking for an exit_code of 0 due to improper mocking causing an exit_code of -1 to be returned instead. This patch set corrects the issue by refactoring the code to allow for exit_code 0 to always be checked. Further refactoring was done in places to reduce code duplication via helpers. Change-Id: Ib9cf7c71b02d74de152b7e34911c867d2251a18a |
||
---|---|---|
doc | ||
images/pegleg | ||
pegleg | ||
site_yamls/site | ||
tests | ||
tools | ||
.dockerignore | ||
.gitignore | ||
.gitreview | ||
.zuul.yaml | ||
LICENSE | ||
Makefile | ||
README.rst | ||
requirements.txt | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Pegleg
Introduction
Pegleg is a document aggregator that provides early linting and validations via Deckhand, a document management micro-service within Airship.
Pegleg supports local and remote Git repositories. Remote repositories can be cloned using a variety of protocols -- HTTP(S) or SSH. Afterward, specific revisions within those repositories can be checked out, their documents aggregated, linted, and passed to the rest of Airship for orchestration, allowing document authors to manage their site definitions using version control.
Find more documentation for Pegleg on Read the Docs.
Core Responsibilities
- aggregation - Aggregates all documents required for site deployment across multiple Git repositories, each of which can be used to maintain separate document sets in isolation
- linting - Configurable linting checks documents for common syntactical and semantical mistakes
Getting Started
For more detailed installation and setup information, please refer to the Getting Started guide.
Integration Points
Pegleg has the following integration points: