* Initial Try of failure retry
* Get failureRetryCount and failureRetryPeriodSecond from command line args.
* Get failureRetryCount and failureRetryPeriodSecond from command line args.
* Get failureRetryCount and failureRetryPeriodSecond from command line args.
* Get failureRetryCount and failureRetryPeriodSecond from command line args.
* Update logic to find out if we should retry.
* 1. add retry wrapper to only argo client.
2. change to env variables instead of command line arguments.
* keep imports grouped
* resolve merge conflict
* Move utils packages that are required for gitops engine under engine/pkg/utils package.
Following changes were implemented:
* util/health package is split into two parts: resource health assessement & resource health assessement and moved into engine/pkg/utils
* utils packages moved: Closer and Close method of util package moved into engine/pkg/utils/io package
* packages diff, errors, exec, json, kube and tracing moved into engine/pkg/utils
* Move single cluster caching into engine/kube/cache package
* move sync functionality to engine/kube/sync package
* remove dependency on metrics package from engine/pkg/utils/kube/cache
* move annotation label definitions into engine/pkg/utils/kube/sync
* make sure engine/pkg has no dependencies on other argo-cd packages
* allow importing engine as a go module
* implement a high-level interface that might be consumed by flux
* fix deadlock caused by cluster cache event handler
* ClusterCache should return error if requested group kind not found
* remove obsolete tests
* apply reviewer notes
The argocd command line supports using the --port-forward options
to allow you to connect to an argocd without an ingress rule. This
is especially useful for command line automation of new environments.
But login doesn't respect port-forward - making it impossible to login
to argocd to be able to later create apps. App creation works fine
with port-forwarding after being able to login.
* fix: Updating to jsonnet v1.15.0 fix issue #3277
* feat: Changes from codegen, adding a repository gt service
* feat: Adding a get repository command
* Retrigger CI pipeline
* refactor: delete deprecated option on Get
refactor printing getcommand result
Getrepository() dependent on rbac enforcement
* fix: setting Get repo command to get
* Set root path
* updated http mux if --rootpath is set during server startup.
updated baseHRef if --rootpath is set.
added --grpc-web-root-path for CLI.
* added rootpath as part of config context name
* clean up not used variables.
* Fixing argocd app diff when using helm repo
* adding test code
* get rid of optional parameter
* get rid of optional parameter
* Added test case
* Fix failed tests
* Fixing could not find plugin issue when app sync and app diff
* Fixing codegen error
* Revert "Fixing codegen error"
This reverts commit b2dcfb81
* Fixing codegen error
* If user is logged in, settings API would return ConfigManagementPlugins
* Add "skip-rbac-setup" flag to "cluster add" command
"InstallClusterManagerRBAC" method of the clusterauth package
is somewhat opinionated about rolebindings and role definitions
for "argocd-manager" SA. Sometimes it is desirable however to manually
pre-configure such bindings and/or modify them in order to comply
with existing infrastructure requirements.
This commit introduces a new option "--skip-rbac-setup" which allows operator
to skip the aforementioned "InstallClusterManagerRBAC" method call.
* Modified --skip-rbac-setup into --service-account flag
* use reference instead of hardoded SA name
Necessary STDIN changes to support Windows
Added support for SE Linux
Informational message about linting OOM
Updated due to latest helm stable being 3.x
* TLA parameters of same time are overwritten
When updating an application deployed with existing TLAs using the following command:
```
argocd app set m2-jsonnet --jsonnet-tla-code "myTLAVar={hello:'world'}"
```
The all the TLAs of type code will be cleared and not preserved as would be expected of a set. The only TLA remaining is `myTLAVar`.
This will set the behavior of TLAs to match that of extVars
Signed-off-by: Daniel Beal <dbeal@wiser.com>
* revert gopkg.lock
* add unit tests
* fix go formatting
Like https://github.com/argoproj/argo-cd/issues/2536 , the DEX password for LDAP is being leaked in a command that prints configuration.
This change not only hides the bindPW but also changes the logging level to trace so that by default, the configuration is not leaked to logs.
