Both these external git repos require their CLI SDK to authenticate. If I am using these services, I am unable to authenticate to view the remote Repo via Diffusion.
Does anyone experience with configuring Diffusion to work with these git Repo types?
I've also now tested it with Visual Studio Online - https://www.visualstudio.com/en-us/version-control-vs
and that works with normal credentials once you have created a 'Personal Access Token' via their GUI.
These are all remote git repos, but AWS and Google, need some kind of Authentication Helpers, which is beyond me at the moment.
What specifically is your use case here? Are you actually using these services or just testing random things?
Looks like AWS does allow SSH connection: http://docs.aws.amazon.com/codecommit/latest/userguide/setting-up-credentials-ssh.html looks like a regular SSH configuration, so it should work.
@chad I'll reiterate, Google, Amazon and Microsoft now offer their own cloud based git repositories. So its a fair shout that in future a fair proportion of private repos will be hosted with 1 of those companies.
I felt like testing them with Diffusion, and those are my results so far.
@avivey, thanks for pointing that out, I was trying via https 'credential helper' but I'll give that a try.
The problem is this falls under "hypothetical" in how we manage feature requests.
https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#hypotheticals
The SSH stuff should work fine. I don't anticipate supporting the HTTP stuff.
If there's additional confusion about this we can eventually have the UI detect these hosts and provide a hint ("Hi, Clippy here! Looks like you're using AWS CodeCommit! Make sure you use SSH to authenticate!").