Alexander Matyushentsev
Alexander Matyushentsev
# Summary Currently, Argo CD and ApplicationSet have implicit dependencies on each other. The ApplicationSet imports Argo CD code and Argo CD Application CRD validation schema. Argo CD bundles ApplicationSet...
Argo CI should be able to handle events from private github repositories
Tracking issue for historical builds data support. Argo CI should automatically remove completed workflows from kubernetes and move to persistent data storage. - [ ] Prepare design document
User should be able to configure webhook using Argo CI management UI instead of doing it manually using Github UI
Argo CI should set branch parameter while launching CI workflow.
# Summary Argo CD supports diffing customization https://argoproj.github.io/argo-cd/user-guide/diffing/ that allows users to better handle well-known limitations and edge cases. # Proposal Migrate Argo CD that implements diffing customization into GitOps...
# Summary Argo CD provides a way to customize resources health assessment using the Lua script. The argocd repository contains library of Lua scripts as well as test framework that...
# Summary After the reflection-based conversion was deprecated in K8S v1.19 the health assessment contains a lot of duplicated code ( see https://github.com/argoproj/gitops-engine/pull/139 ). We should consider using `unstructured` package...
The synchronization process is controlled by the following annotations: * argocd.argoproj.io/sync-wave * argocd.argoproj.io/hook * argocd.argoproj.io/hook-delete-policy * argocd.argoproj.io/sync-wave We should get rid of `argocd` part since the engine is not specific...
By @AlexDHoffer: https://github.com/argoproj-labs/argocd-notifications/issues/240 Some existing CD systems e.g. Jenkins can post build results to Jira issues as well as natively link commits in the build to those issues. See here...