Mateusz Suski 78bcfce43a
ci / validate (push) Failing after 2m0s
Refactor Ansible playbooks to comply with best practices and fix linting violations
- Implement 4-role architecture (base_provision, patching, hardening, decommission)
- Extract hardcoded values to role defaults and group_vars
- Add Ansible Vault integration for secrets management
- Implement proper handlers for service restarts instead of direct tasks
- Add Molecule testing framework with Docker driver
- Configure ansible-lint with production profile settings

Fix all 125+ ansible-lint violations:
- Add FQCN (Fully Qualified Collection Names) to all modules
- Replace yes/no with true/false for boolean values
- Add explicit mode parameters to file/template operations
- Remove duplicate post_tasks blocks from playbooks
- Add newlines at end of all YAML files
- Fix key ordering in tasks (name, when, block)
- Convert service restarts to handlers with notify
- Remove ignore_errors in favor of failed_when/changed_when
- Fix line length violations and empty lines
- Add noqa comments for unavoidable risky-file-permissions

Update documentation:
- Add REFACTORING.md with implementation details
- Add VAULT_GUIDE.md for secrets management
- Add per-role README.md files
- Update existing documentation

All playbooks now pass ansible-lint production profile with 0 violations.
2026-05-04 09:13:25 +00:00

Infrastructure Engineering Portfolio

This repository contains independent infrastructure projects focused on automation, migration assurance, and observability. The projects are intentionally small enough to run locally, but structured around the operating patterns used in enterprise platform teams: repeatable workflows, clear evidence artifacts, and operational documentation.

Projects

  • Enterprise Infrastructure Simulator - Ansible-driven lifecycle operations for provisioning, patching, hardening, decommissioning, and failure simulation across Linux nodes.
  • Migration Validation Framework - Python CLI for collecting before/after system snapshots and producing structured migration comparison results.
  • Observability Stack - Docker Compose based logging and dashboard stack with alert rules, sample logs, and incident simulation.

Skills Demonstrated

  • Infrastructure automation with Ansible
  • Operational scenario design and incident simulation
  • Migration validation, drift detection, and JSON reporting
  • Docker Compose service validation
  • Repository hygiene, CI checks, and professional project documentation

Each project remains independent and includes its own README, architecture notes, examples, and runnable scenarios.

S
Description
No description provided
Readme 1.6 MiB
Languages
Shell 55.4%
Python 42.8%
Jinja 1.6%
PHP 0.2%