This package is designed for use as part of a UDS Software Factory bundle deployed on UDS Core.
SonarQube needs connection to a PostgreSQL instance either in cluster or external. It finds this connection via the sonarqube_db_endpoint variable declared in the zarf package and configured (as an example) at deploy time by the uds bundle config.
For local testing and CI, SonarQube is bundled with the dev-postgres package.
| Flavor | Description | Example Creation |
|---|---|---|
upstream |
Uses upstream images within the package | zarf package create . -f upstream |
registry1 |
Uses images from registry1.dso.mil within the package | zarf package create . -f registry1 |
NOTE:
registry1flavor only supports the amd64 architecture
The released packages can be found in ghcr.
*For local dev, this requires you install uds-cli
✅ Tip: To get a list of tasks to run you can use
uds run --list!
Please see the CONTRIBUTING.md
This package is currently using registry1 chart for both flavors. This is because the upstream chart depends on 'hostname' and 'wget' to be available in the images, and the registry1 images do not include these tools.
When developing this package it is ideal to utilize the json schemas for UDS Bundles, Zarf Packages and Maru Tasks. This involves configuring your IDE to provide schema validation for the respective files used by each application. For guidance on how to set up this schema validation, please refer to the guide in uds-common.