v0.5.1

• API server incorrectly compose application fully qualified name for RBAC check (#283)
• UI crash while rendering application operation info if operation failed

v0.5.0

• RBAC access control
• Repository/Cluster state monitoring
• ArgoCD settings import/export
• Application creation UI wizard
• argocd app manifests for printing the application manifests
• argocd app unset command to unset parameter overrides

• Fail app sync if prune flag is required (#276)
• Take into account number of unavailable replicas to decided if deployment is healthy or not #270
• Repo names containing underscores were not being accepted (#258)
• Cookie token was not parsed properly when mixed with other site cookies
• Add ability to show parameters and overrides in CLI (resolves #240)

v0.4.7

• Fix argocd app wait health checking logic

v0.4.6

• Retry argocd app wait connection errors from EOF watch. Show detailed state changes

v0.4.5

• Add argocd app unset command to unset parameter overrides

• Cookie token was not parsed properly when mixed with other site cookies

v0.4.4

• Add ability to show parameters and overrides in CLI (resolves #240)
• Add Events API endpoint
• Issue #238 - add upsert flag to 'argocd app create' command
• Add repo browsing endpoint (#229)
• Support subscribing to settings updates and auto-restart of dex and API server

• Issue #233 - Controller does not persist rollback operation result
• App sync frequently fails due to concurrent app modification

v0.4.3

• Move local branch deletion as part of git Reset() (resolves #185) (#222)
• Fix exit code for app wait (#219)

v0.4.2

• Remove interactive context name prompt during login which broke login automation
• Show URL in argocd app get
• Rename force flag to cascade in argocd app delete

v0.4.1

• Implemented argocd app wait command

v0.4.0

v0.4.0 (2018-05-17)

• SSO Integration
• GitHub Webhook
• Add application health status
• Sync/Rollback/Delete is asynchronously handled by controller

• Refactor CRUD operation on clusters and repos
• Sync will always perform kubectl apply
• Synced Status considers last-applied-configuration annotatoin
• Server & namespace are mandatory fields (still inferred from app.yaml)
• Manifests are memoized in repo server

• Fix connection timeouts to SSH repos