You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched the issue queue to verify this is not a duplicate bug report.
I've included steps to reproduce the bug.
I've pasted the output of kargo version.
I've pasted logs, if applicable.
Description
When using kustomize with a remoteBase targeting to a private repository (in our case Github Enterprise), credentials are needed for authentication. With ArgoCD repoServer as well as with local kustomize client, credentials are passed through
.
"kargo-render" howerver, do not pass through the credentials properly so that it prompts again for git credentials, even though they are provided from a credential store.
This results simply in failed promotions via Kargo Controller and an error message in the logs (see below).
When running kargo-render locally within a container it fails as well when no credentials are provided, but would succeed if they are provided a 2nd time as a user-input.
I understood that kargo-renders future is unknown, and it might end up fully in Kargo 0.9+, Therefore I want to highlight this bug here to be directly covered in the potentially integration, since we are heavily relying in using kustomize remotebases
Expected behavior:
Kargo/Kargo-render handles git credentials similar like ArgoCD does in order to support kustomize remote bases targeting private repositories
Error: error pre-rendering manifests: error generating manifests using Argo CD repo server: `kustomize build /tmp/repo-311868286/repo/applications/cortex-argoevents-manifest/stages/kube1-dev` failed exit status 1: Error: accumulating resources: accumulating resources from 'https://my-company/my-org/cortex-argoevents-manifest.git//deployment?ref=HEAD': MalformedYAMLError: yaml: line 184: mapping values are not allowed in this context in File: https://my-company/my-org/cortex-argoevents-manifest.git//deployment?ref=HEAD
Version
version: 0.8.4
Logs
Paste any relevant application logs here.
The text was updated successfully, but these errors were encountered:
Checklist
kargo version
.Description
When using
kustomize with a remoteBase targeting to a private repository
(in our case Github Enterprise), credentials are needed for authentication. With ArgoCD repoServer as well as with local kustomize client, credentials are passed through.
"kargo-render" howerver, do not pass through the credentials properly so that it prompts again for git credentials, even though they are provided from a credential store.
This results simply in failed promotions via Kargo Controller and an error message in the logs (see below).
When running kargo-render locally within a container it fails as well when no credentials are provided, but would succeed if they are provided a 2nd time as a user-input.
I understood that kargo-renders future is unknown, and it might end up fully in Kargo 0.9+, Therefore I want to highlight this bug here to be directly covered in the potentially integration, since we are heavily relying in using kustomize remotebases
Expected behavior:
Kargo/Kargo-render handles git credentials similar like ArgoCD does in order to support kustomize remote bases targeting private repositories
Screenshots
Steps to Reproduce
Example:
kargo-render.yaml
kustomization
local command
prompts for:
and if not provided it fails with error
Version
Logs
The text was updated successfully, but these errors were encountered: