{"action":"created","issue":{"url":"https://api.github.com/repos/roboll/helmfile/issues/49","repository_url":"https://api.github.com/repos/roboll/helmfile","labels_url":"https://api.github.com/repos/roboll/helmfile/issues/49/labels{/name}","comments_url":"https://api.github.com/repos/roboll/helmfile/issues/49/comments","events_url":"https://api.github.com/repos/roboll/helmfile/issues/49/events","html_url":"https://github.com/roboll/helmfile/issues/49","id":303851510,"number":49,"title":"Oneshot jobs","user":{"login":"mumoshu","id":22009,"avatar_url":"https://avatars0.githubusercontent.com/u/22009?v=4","gravatar_id":"","url":"https://api.github.com/users/mumoshu","html_url":"https://github.com/mumoshu","followers_url":"https://api.github.com/users/mumoshu/followers","following_url":"https://api.github.com/users/mumoshu/following{/other_user}","gists_url":"https://api.github.com/users/mumoshu/gists{/gist_id}","starred_url":"https://api.github.com/users/mumoshu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mumoshu/subscriptions","organizations_url":"https://api.github.com/users/mumoshu/orgs","repos_url":"https://api.github.com/users/mumoshu/repos","events_url":"https://api.github.com/users/mumoshu/events{/privacy}","received_events_url":"https://api.github.com/users/mumoshu/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-03-09T14:05:08Z","updated_at":"2018-03-09T15:45:20Z","closed_at":null,"author_association":"COLLABORATOR","body":"I'm a bit hesitant to propose this but how about supporting oneshot jobs in helmfile?\r\n\r\nAn oneshot job can be either a K8S job or a pod created via `helm upgrade --install` to accomplish a job like db migration, enqueueing a large job to a kind of workflow system, etc.\r\n\r\nAs of today, we have to resort a variant of `kubectl run --image $img` to run an oneshot job, even in a situation that our regular app are managed by helm and shared the image, envvars with oneshot jobs.\r\n\r\nAFAIK, there's no such tool to support this use-case. And supporting it in helmfile allows us to provide a more docker-compose-like U/X to helm users, but the docker-build feature.\r\n\r\nThoughts?\r\n\r\ncc/ @roboll @sstarcher "},"comment":{"url":"https://api.github.com/repos/roboll/helmfile/issues/comments/371849910","html_url":"https://github.com/roboll/helmfile/issues/49#issuecomment-371849910","issue_url":"https://api.github.com/repos/roboll/helmfile/issues/49","id":371849910,"user":{"login":"sstarcher","id":3778974,"avatar_url":"https://avatars0.githubusercontent.com/u/3778974?v=4","gravatar_id":"","url":"https://api.github.com/users/sstarcher","html_url":"https://github.com/sstarcher","followers_url":"https://api.github.com/users/sstarcher/followers","following_url":"https://api.github.com/users/sstarcher/following{/other_user}","gists_url":"https://api.github.com/users/sstarcher/gists{/gist_id}","starred_url":"https://api.github.com/users/sstarcher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sstarcher/subscriptions","organizations_url":"https://api.github.com/users/sstarcher/orgs","repos_url":"https://api.github.com/users/sstarcher/repos","events_url":"https://api.github.com/users/sstarcher/events{/privacy}","received_events_url":"https://api.github.com/users/sstarcher/received_events","type":"User","site_admin":false},"created_at":"2018-03-09T15:45:20Z","updated_at":"2018-03-09T15:45:20Z","author_association":"NONE","body":"@mumoshu ya in that situation #28 should give the main portion.  As for tailing the logs that could be a nice feature, but it would likely best be supported under a separate issue and maybe with a flag of `--follow` or such, but that's a good bit more of a complicated situation."}}
{"actor":{"display_login":"sstarcher"}}