{"action":"closed","issue":{"url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/941","repository_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin","labels_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/941/labels{/name}","comments_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/941/comments","events_url":"https://api.github.com/repos/fabric8io/fabric8-maven-plugin/issues/941/events","html_url":"https://github.com/fabric8io/fabric8-maven-plugin/issues/941","id":228999200,"number":941,"title":"Add Kompose support","user":{"login":"rhuss","id":99080,"avatar_url":"https://avatars3.githubusercontent.com/u/99080?v=4","gravatar_id":"","url":"https://api.github.com/users/rhuss","html_url":"https://github.com/rhuss","followers_url":"https://api.github.com/users/rhuss/followers","following_url":"https://api.github.com/users/rhuss/following{/other_user}","gists_url":"https://api.github.com/users/rhuss/gists{/gist_id}","starred_url":"https://api.github.com/users/rhuss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhuss/subscriptions","organizations_url":"https://api.github.com/users/rhuss/orgs","repos_url":"https://api.github.com/users/rhuss/repos","events_url":"https://api.github.com/users/rhuss/events{/privacy}","received_events_url":"https://api.github.com/users/rhuss/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2017-05-16T11:27:57Z","updated_at":"2017-11-10T08:37:32Z","closed_at":"2017-11-10T08:37:32Z","author_association":"CONTRIBUTOR","body":"[Kompose](http://kompose.io/) is an awesome conversion tool which creates Kubernetes descriptor objects from [Docker compose](https://docs.docker.com/compose/) files.\r\n\r\nThe idea is to extend the `fabric8:resource` goal to support Docker compose files via an external CLI call to `kompose`. This should be possible to be switched on either explicitly by a configuration option `<composeFile>` in the XML configuration or maybe even implicitly by monitoring a directory `src/main/fabric8-kompose` for the content of some `docker-compose.yml` files.\r\n\r\nThe flow would be:\r\n\r\n* If enabled and present, `kompose` is called externally which creates Kubernetes resource descriptor yaml files in a build directory below `target/fabric8`. Configuration for `kompose` comes from the plugin configuration.\r\n* These descriptors are read in by f-m-p via the kubernetes client\r\n* The so instantiated `KubernetesList` is then used as starting point for the further processing:\r\n  - Additional fragments can be added\r\n  - Information of the XML configuration can add to this list\r\n  - The enricher chain is fed with this list so that it can be enriched as usual.\r\n\r\nAn alternative approach would be to re-implement kompose functionality in Java which would provide a better integration (no external tool is required) but is much more work.\r\n\r\n@jstrachan @pradeepto wdyt ? Is this a feasible plan ? Or do you see a better integration point ?\r\n"}}
{"actor":{"display_login":"hrishin"}}