{"action":"opened","issue":{"url":"https://api.github.com/repos/criecm/ansible-iocage/issues/13","repository_url":"https://api.github.com/repos/criecm/ansible-iocage","labels_url":"https://api.github.com/repos/criecm/ansible-iocage/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/criecm/ansible-iocage/issues/13/comments","events_url":"https://api.github.com/repos/criecm/ansible-iocage/issues/13/events","html_url":"https://github.com/criecm/ansible-iocage/issues/13","id":278721241,"number":13,"title":"Iocage vs iocell, and unified support in ansible?","user":{"login":"Infiniverse","id":2773422,"avatar_url":"https://avatars1.githubusercontent.com/u/2773422?v=4","gravatar_id":"","url":"https://api.github.com/users/Infiniverse","html_url":"https://github.com/Infiniverse","followers_url":"https://api.github.com/users/Infiniverse/followers","following_url":"https://api.github.com/users/Infiniverse/following{/other_user}","gists_url":"https://api.github.com/users/Infiniverse/gists{/gist_id}","starred_url":"https://api.github.com/users/Infiniverse/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Infiniverse/subscriptions","organizations_url":"https://api.github.com/users/Infiniverse/orgs","repos_url":"https://api.github.com/users/Infiniverse/repos","events_url":"https://api.github.com/users/Infiniverse/events{/privacy}","received_events_url":"https://api.github.com/users/Infiniverse/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-12-02T21:55:36Z","updated_at":"2017-12-02T21:55:36Z","closed_at":null,"author_association":"NONE","body":"Hey there,\r\n\r\nI'm in a world of pain after the iocage split into iocell and the new py-iocage.\r\n\r\nThe later is still immature, and lacks some critical features that the original (stable, but unsupposed) version did. We're currently somewhere between iocage and iocell.\r\n\r\nI'm unsure now which version of ansible-iocage I should be hacking on. I'm guessing that this one is now tracking the python version. The old version was renamed to ansible-iocell, but I'm not sure it had the various bug fixed applied that we had fixed earlier in the year. :/\r\n\r\nWhat to do? Do you think it might be sensible to have a single ansible driver that supports both iocell and iocage, so that those of us with load of things already in production have flexiblity?"}}
{"actor":{"display_login":"Infiniverse"}}