fix: align portal-tenants ApplicationSet repoURL to SSH#23
Merged
Conversation
The portal worker's git layer is SSH-only — it pushes rendered tenant manifests to the tenants GitOps repo over SSH (git@github.com:nanohype/tenants.git). This ApplicationSet pointed at the HTTPS URL for both the directory generator and the template source, so ArgoCD and the portal disagreed on the repo identity and a registered SSH credential wouldn't match. Flips both repoURLs to the SSH form so producer (portal push) and consumer (ArgoCD pull) reference the same repo, and documents that ArgoCD needs a matching SSH repo credential (a read-only deploy key on the private tenants repo) registered for this URL.
CI Results
All validations passed. |
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
1 participant
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.
The portal worker's git layer is SSH-only and pushes rendered tenant manifests to
git@github.com:nanohype/tenants.git. This ApplicationSet used the HTTPS URL for both the directory generator and the template source, so ArgoCD and the portal disagreed on repo identity and an SSH credential wouldn't match.Flips both repoURLs to the SSH form so producer (portal push) and consumer (ArgoCD pull) reference the same repo. Documents that ArgoCD needs a matching SSH repo credential (read-only deploy key on the private tenants repo) registered for this URL — the remaining consumer-half runtime step.