helmfile/state
KUOKA Yusuke 0534117b62
feat: postsync hooks (#601)
`postsync` events are triggered after each release is applied to the cluster in `helmfile sync` or `helmfile apply`.

This should be a best hook to notify only after each sync failed or succeeded. This can be used for running operations like patching K8s resources managed by helm, but that should be the last-resort. Maybe you should fork/update the chart, or submit a feature request to add `replicated/ship` integration to `helmfile` in that case :)

Resolves #599
2019-05-16 21:24:16 +09:00
..
chart_dependency.go feat: support for locking the same chart for two or more versions (#600) 2019-05-16 21:19:30 +09:00
create.go feat: "bases" for easier layerina 2019-05-13 21:48:00 +09:00
create_test.go feat: "bases" for easier layerina 2019-05-13 21:48:00 +09:00
environment.go feat: Environment Secrets (#274) 2018-09-02 21:07:35 +09:00
release.go fix: `helmfile diff` should not leave temp values files (#525) 2019-04-01 22:24:18 +09:00
release_error.go Various U/X improvements for `helmfile apply` (#586) 2019-05-12 16:26:11 +09:00
release_filters.go fix: prevent panicing on invalid selector format (#323) 2018-09-09 17:20:44 +09:00
state.go feat: postsync hooks (#601) 2019-05-16 21:24:16 +09:00
state_exec_tmpl.go feat: Release Template (#439) 2019-01-22 01:19:07 +09:00
state_exec_tmpl_test.go feat: Release Template (#439) 2019-01-22 01:19:07 +09:00
state_run.go Simple implementation of the tillerless mode (#531) 2019-04-05 19:02:37 +09:00
state_test.go feat: support for locking the same chart for two or more versions (#600) 2019-05-16 21:19:30 +09:00
types.go feat: Release Template (#439) 2019-01-22 01:19:07 +09:00