Answers in-line. 2017-02-06 6:36 GMT+01:00 Andrew Wilkins <[email protected]>: > > > Very cool, thanks for sharing. > > A few things which I think would make this even better: > - integration with Ubuntu SSO (or GitHub OAuth, etc.) >
This will probably be the most difficult task. Eclipse Che doesn't have any authentication mechanism builtin. Each user has to have their own Eclipse Che instance. Codenvy is a commercial product based on Eclipse Che that has authentication builtin, but it is closed-source. > - with above: inject macaroon/token into the charmbox container, so that > the juju CLI would be automatically logged in (would only work with > external identity management) > Yes, that would be awesome! Even without the above, we might be able to do it by supplying a token to the Che Charm. > - with above: Right-click "Deploy to Juju", with detection of changes to > deployed code and an option to update. > > YES! The Che team is working on a feature called "smart commands <https://github.com/eclipse/che/issues/2681>". This will allow us to create stuff like a `build charm` action that appears in the right-click menu of a layer, a `build charm` command that build the currently selected layer, a `deploy charm` command that deploys/updates the charm. Che's speed of development is really fast, and they seem to be going in a direction that will allow us to create deep integration between Juju and Che. > ... in case anyone has spare time ;) > > Cheers, > Andrew >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
