feat(argocd-understack): refactor deployment directory layout#1655
Merged
Conversation
cardoe
force-pushed
the
argocd-understack-relayout
branch
from
February 4, 2026 14:41
3eb2a5d to
d8dcb34
Compare
cardoe
force-pushed
the
argocd-understack-relayout
branch
from
February 4, 2026 14:52
d8dcb34 to
fa92c16
Compare
abhimanyu003
reviewed
Feb 4, 2026
abhimanyu003
approved these changes
Feb 4, 2026
skrobul
approved these changes
Feb 4, 2026
skrobul
left a comment
skrobul
left a comment
Collaborator
There was a problem hiding this comment.
few comments, but overall lgtm
This introduces three new understackctl deploy subcommands to streamline deployment repository management. The deploy init command creates a cluster directory with a deploy.yaml configuration file that follows the ArgoCD Helm chart values structure, where each component has an individual enabled flag. Component names use underscores in the YAML to match Helm conventions. The deploy update command syncs the filesystem by creating manifests directories for enabled components and removing directories for disabled ones, automatically generating kustomization.yaml and values.yaml files in each component directory. The deploy check command validates that all required files exist for enabled components. These commands replace the manual directory creation and gitops-deploy.sh script workflow previously documented. The ArgoCD chart templates are updated to look for Helm values at manifests/component/values.yaml instead of helm-configs/component.yaml, consolidating all component configuration into a single manifests directory structure. This allows Kustomize resources and Helm values to coexist in the same component directory, simplifying the deployment repository layout. Documentation is updated throughout the deploy guide to use the new understackctl commands instead of manual mkdir and file creation steps. The gitops-deploy.sh script is deprecated with a notice directing users to the new CLI commands. A GitHub Actions workflow is added to run Go tests for all Go projects in the repository, ensuring the new deploy commands remain tested in CI.
cardoe
force-pushed
the
argocd-understack-relayout
branch
from
February 4, 2026 18:17
fa92c16 to
906350b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This introduces three new understackctl deploy subcommands to
streamline deployment repository management. The deploy init command
creates a cluster directory with a deploy.yaml configuration file that
follows the ArgoCD Helm chart values structure, where each component
has an individual enabled flag. Component names use underscores in
the YAML to match Helm conventions. The deploy update command syncs
the filesystem by creating manifests directories for enabled
components and removing directories for disabled ones, automatically
generating kustomization.yaml and values.yaml files in each component
directory. The deploy check command validates that all required files
exist for enabled components. These commands replace the manual
directory creation and gitops-deploy.sh script workflow previously
documented.
The ArgoCD chart templates are updated to look for Helm values at
manifests/component/values.yaml instead of helm-configs/component.yaml,
consolidating all component configuration into a single manifests
directory structure. This allows Kustomize resources and Helm values
to coexist in the same component directory, simplifying the deployment
repository layout.
Documentation is updated throughout the deploy guide to use the new
understackctl commands instead of manual mkdir and file creation
steps. The gitops-deploy.sh script is deprecated with a notice
directing users to the new CLI commands. A GitHub Actions workflow
is added to run Go tests for all Go projects in the repository,
ensuring the new deploy commands remain tested in CI.