Assigned
Status Update
Comments
pa...@google.com <pa...@google.com> #2
Could you clarify a bit more what you'd like to see this page do? Maybe with some screenshots or documentation links for Codenvy?
Jo...@thp.org <Jo...@thp.org> #3
I would like to be able to use my google source repository as a remote git repository without having to install the gcloud sdk. The only instructions at google for authenticating start with "install gcloud sdk..." and then issue gcloud commands.
Here is the Codenvy reference to adding repositories:https://eclipse-che.readme.io/docs/git#section-other-git-hosting-providers (at the bottom). I've attached a screenshot.
Here is the Codenvy reference to adding repositories:
ng...@google.com <ng...@google.com> #4
Thanks for clarifying your request.
Part of this challenge is because, as stated in the documentation[1], the credential helper script uses your 'Google account credentials' to authenticate git and not an uploaded SSH key.
For your SSH authentication request to work, there would need to be some mechanism for uploading a standard SSH public key and associating it with a given Cloud Source repository. Your cloud IDE would then be able to authenticate and push changes assuming it had the corresponding key.
As this mechanism does not currently exist, I've forwarded your request the engineering team. Any questions they may have on this feature will be posted here. Updates maybe posted here as well.
In the meantime, I would suggest two possible workarounds:
1. Install the gcloud SDK on your Codenvy development environment. I realize you've explicitly stated wanting to avoid this but this is a definite way of achieving your goal. This will allow you to push changes to the Google-host git repo using the terminal window if the IDE as well use all the other gcloud commands for managing your application. As far as I remember, Codenvy does allow users to install applications inside the provisioned Docker containers for development. Thus:
> sudo apt-get install google-cloud-sdk
2. Alternatively, you could use a remote repo with Bitbucket (who offer private repositories) and mirror it with Cloud Source Repository[2]. Pushes to the Bitbucket repository will be reflected in the Cloud Source repo and commits to the Cloud Source repo will be reflected in the Bitbucket repo so it would essentially function as a proxy.
Hope the above helps! Since I've changed your original feature request slightly to address the root cause, please let me know if the above does not reflect your request or misrepresents it.
[1]:https://cloud.google.com/source-repositories/docs/adding-repositories-as-remotes#adding_the_repository_as_a_remote
[2]:https://cloud.google.com/source-repositories/docs/connecting-hosted-repositories
Part of this challenge is because, as stated in the documentation[1], the credential helper script uses your 'Google account credentials' to authenticate git and not an uploaded SSH key.
For your SSH authentication request to work, there would need to be some mechanism for uploading a standard SSH public key and associating it with a given Cloud Source repository. Your cloud IDE would then be able to authenticate and push changes assuming it had the corresponding key.
As this mechanism does not currently exist, I've forwarded your request the engineering team. Any questions they may have on this feature will be posted here. Updates maybe posted here as well.
In the meantime, I would suggest two possible workarounds:
1. Install the gcloud SDK on your Codenvy development environment. I realize you've explicitly stated wanting to avoid this but this is a definite way of achieving your goal. This will allow you to push changes to the Google-host git repo using the terminal window if the IDE as well use all the other gcloud commands for managing your application. As far as I remember, Codenvy does allow users to install applications inside the provisioned Docker containers for development. Thus:
> sudo apt-get install google-cloud-sdk
2. Alternatively, you could use a remote repo with Bitbucket (who offer private repositories) and mirror it with Cloud Source Repository[2]. Pushes to the Bitbucket repository will be reflected in the Cloud Source repo and commits to the Cloud Source repo will be reflected in the Bitbucket repo so it would essentially function as a proxy.
Hope the above helps! Since I've changed your original feature request slightly to address the root cause, please let me know if the above does not reflect your request or misrepresents it.
[1]:
[2]:
Jo...@thp.org <Jo...@thp.org> #5
Thanks so much for this update. I've done the mirroring workaround with github for the time being, although I would prefer to only have to work directly with one repository rather than two. Perhaps one day Google will provide a full cloud-based development platform. It seems like the components are all there, and hosting your own version of the open-source eclipse/che as your code editor would make my life much easier!
pa...@google.com <pa...@google.com> #6
Thanks for making this feature request. We've logged a feature request to allow uploading of SSH public keys for Cloud Source Repositories as opposed to using gcloud auth. We will update this thread with any progress updates.
ng...@google.com <ng...@google.com>
[Deleted User] <[Deleted User]> #7
delete
Description
Web page to generate keys for use with IDEs like Codenvy.
What business case or problem would this feature help you to solve?
It would be fairly difficult to install the gcloud sdk on these online IDEs in order to authenticate.
What workarounds or alternatives have you considered? In what way were
these unsuitable for your needs?
Not using the source repos, which is not a very good one.
What version of the product are you using? On what operating system?
Current source repos from my chromebook.
Please provide any additional information below.