search

defenseunicorns / uds-package-sonarqube

🏭 UDS Sonarqube Zarf Package
Apache License 2.0
3 stars 2 forks source link

Update sonarqube repo to utilize zarf composability to keep the configuration DRY #43

Closed zachariahmiller closed 7 months ago

zachariahmiller commented 7 months ago

Describe what should be investigated or refactored

A standard we have developed for uds packages is to have common zarf components defines in a common/zarf.yaml and then have the flavor specific components import that common component. This keeps the configuration DRY and is easier to update.

Links to any relevant code

As an example look at the gitlab package: Common Importing common into flavored components

This change also entails breaking values out into three sets, upstream-values.yaml (only includes image bits for upstream flavor), registry1-values.yaml (only includes image bits for registry1 flavor), and values (or common values) which contains the rest of the base values configuration. The flavor specific ones are imported in the root level flavor components and the common values is imported in the component in common/zarf.yaml

Additional context

If you have questions ask :)