* add icon in app table view Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * use defaut menu in tree-grouped Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * use default menu in pod views Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * fix custom delete actions Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * menu item in list Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * fix pod wrongly identified as root in network graph Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * update docs error Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * call delete pod action if kind is pod Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * add logs action to pods Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * delete in app details Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * use managed instead of root for menu items Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * lint fix Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * fix lint again Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * feat(ui): list dependent resources in delete popup Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * linting Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * childs to children Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> * update ui dep Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com> --------- Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
1.9 KiB
Managing Dependencies
GitOps Engine (github.com/argoproj/gitops-engine)
Repository
https://github.com/argoproj/gitops-engine
Pulling changes from gitops-engine
After your GitOps Engine PR has been merged, ArgoCD needs to be updated to pull in the version of the GitOps engine that contains your change. Here are the steps:
-
Retrieve the SHA hash for your commit. You will use this in the next step.
-
From the
argo-cdfolder, run the following commandgo get github.com/argoproj/gitops-engine@<git-commit-sha>If you get an error message
invalid version: unknown revisionthen you got the wrong SHA hash -
Run:
go mod tidy -
The following files are changed:
go.modgo.sum
-
Create an ArgoCD PR with a
refactor:type in its title for the two file changes.
Tips:
- See https://github.com/argoproj/argo-cd/pull/4434 as an example
- The PR might require additional, dependent changes in ArgoCD that are directly impacted by the changes made in the engine.
Argo UI Components
Repository
https://github.com/argoproj/argo-ui
Pulling changes from Argo UI into Argo CD
If you make changes to the Argo UI component, and your Argo CD changes depend on those changes, follow these steps:
- Make changes to Argo UI and submit the PR request.
- Also, prepare your Argo CD changes, but don't create the PR just yet.
- After the Argo UI PR has been merged to master, then as part of your Argo CD changes:
- Run
yarn add git+https://github.com/argoproj/argo-ui.gitin theui/directory, and then, - Check in the regenerated yarn.lock file as part of your Argo CD commit
- Run
- Create the Argo CD PR when you are ready. The PR build and test checks should pass.
If your Argo UI change is a 'stand-alone' fix, and you simply want Argo CD to pull in your change, then simply create an Argo CD PR with the yarn.lock file change.