How colav/impactu works
Project type and purpose
• From the file tree and the README (“Colav Impactu Issues and Documentation”), this is not a typical full-stack service but a DevOps/CI-CD-orchestration repository. It centralizes:
• Configuration files per environment (configs/)
• Documentation (doc/)
• Release notes (releases/)
• Workflow definitions (workflows/)
• Its purpose is to store and version “Impactu” pipeline definitions (kahi_impactu…yml), environment configs (oxomoc/colombia_config.py), sample pipelines (workflows/samples), and documentation for Colav’s Impactu process and integration (e.g., with DSpace).
File structure
• Top-level directories:
• configs/oxomoc – environment-specific Python config
• doc/ – Markdown files capturing processes, data-product definitions
• releases/ – human-readable release notes by date/language
• workflows/impactu – pipeline-as-code YAMLs for production/dev/Dspace
• workflows/samples – sample workflows and README
• No application “src/” folder: this repo’s “runtime” is the CI/CD system (e.g., GitHub Actions or an orchestration engine) that reads these workflows.
• Key files: .gitignore, LICENSE, README.md
README for additional insights
• Confirms that the repo serves as both an “issues and documentation” hub.
Detail
• Separate workflow paths (prod vs dev vs sample) if space permits.
• Call out the config file lookup step in the pipeline.
Layer 1: Developer → Git Repo
Layer 2: CI/CD Runner (pipeline engine)
Layer 3: External Services (Impactu, DSpace, Sample)
Layer 4: Artifacts (releases/, published docs)