mirror of
https://github.com/argoproj/argo-cd
synced 2026-04-21 17:07:16 +00:00
efc8ec1d78
When creating an application directly through the CLI or a `kubectl
apply`, it's relatively obvious which application is invalid (provided
you aren't applying several at once) as you're there creating it
interactively.
It's less clear when applications are generated by the application set
controller. When that happens, you need to go looking in the controller
logs, where you'll find something like:
> time="2021-08-10T11:36:02Z" level=error msg="application spec is
> invalid: InvalidSpecError: application destination
> {https://kubernetes.default.svc default} is not permitted in project
> 'my-project'"
which doesn't have any connection back to the application being
generated. This is particularly tricky to track down if you're searching
your logs via some sort of aggregator rather than watching `kubectl logs
-f`.
After this change, the log produced would be:
> time="2021-08-10T11:36:02Z" level=error msg="application spec for
> guestbook is invalid: InvalidSpecError: application destination
> {https://kubernetes.default.svc default} is not permitted in project
> 'my-project'"
There's probably fancier ways this information could be presented (e.g.
if application sets were represented in the UI and knew about failures
to apply their generated applications), but this logging change seems
like a cheap way to make this situation more debuggable.
Signed-off-by: Chris Sinjakli <chris@sinjakli.co.uk>
|
||
|---|---|---|
| .. | ||
| application.go | ||
| application.proto | ||
| application_test.go | ||
| broadcaster.go | ||
| broadcaster_test.go | ||
| logs.go | ||
| logs_test.go | ||