Harvester Golden Images
D 56 completed
Other
infrastructure / shell · tiny
42
Files
3,566
LOC
0
Frameworks
5
Languages
Pipeline State
completedRun ID
#1542525Phase
doneProgress
0%Started
2026-04-16 21:28:32Finished
2026-04-16 21:28:32LLM tokens
0Pipeline Metadata
Stage
CatalogedDecision
proceedNovelty
33.34Framework unique
—Isolation
—Last stage change
2026-05-10 03:35:31Deduplication group #49132
Member of a group with 28 similar repo(s) — canonical #295729 view group →
Repobility — the code-quality scanner for AI-generated software · https://repobility.com
AI Prompt
Create a set of infrastructure automation scripts for building "Golden Images" for Harvester HCI. I need a system that can produce pre-configured, hardened QCOW2 images. The process should involve using a build script, potentially leveraging Terraform, to manage the creation and import of images like CIS-Hardened (for Rocky 9, Debian 12, Ubuntu 24.04, Fedora 42) and RKE2 Nodes. The scripts should handle configuration steps like copying example variables, running the build process (e.g., `./build.sh build all`), and listing or deleting existing images. Please structure the necessary YAML, shell, and configuration files to support this workflow.
shell infrastructure yaml terraform ci automation qcow2 harvester linux
Generated by gemma4:latest
Catalog Information
Create a set of infrastructure automation scripts for building "Golden Images" for Harvester HCI. I need a system that can produce pre-configured, hardened QCOW2 images. The process should involve using a build script, potentially leveraging Terraform, to manage the creation and import of images like CIS-Hardened (for Rocky 9, Debian 12, Ubuntu 24.04, Fedora 42) and RKE2 Nodes. The scripts should handle configuration steps like copying example variables, running the build process (e.g., `./build
Tags
shell infrastructure yaml terraform ci automation qcow2 harvester linux
Quality Score
D
55.9/100
Structure
48
Code Quality
80
Documentation
49
Testing
15
Practices
66
Security
66
Dependencies
50
Strengths
- CI/CD pipeline configured (github_actions)
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
- Potential hardcoded secrets in 1 files
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
- Move hardcoded secrets to environment variables or a secrets manager
Languages
Frameworks
None detected
Embed Badge
Add to your README:
