Assigned
Status Update
No update yet.
Comments
ca...@google.com
Hi, could you please share screen shots of the UI you refer? Currently in the Cloud Source Repositories UI, in the top you will find:
YourRepository > Branch > file
You have a drop down in Repository and in Branch to change anytime.
kp...@theembassyvfx.com
Hey! Thanks for taking a look at this. I have attached a screenshot of the home page of a Cloud Source Repository with the UI you mentioned open. You will see the main area says "No commits on the default branch." The default branch in this case is "main" (I am assuming that Cloud Source Repositories is expecting it to be "master"). As I mentioned in my original post, this is the naming system that github recommends and that they will be using by default starting 10/1/2020 (https://github.com/github/renaming ). I refer to github as an example because the repository in the screenshot is a mirror of a github repo, that has "main" as the default branch and no "master" branch.
ma...@gmail.com
Hi, this feature request has been forwarded to the Source Repository product management team so that they may evaluate it. There is no timeline or implementation guarantee for feature requests. All communication regarding this feature request is to be done here.
Description
The first place I looked was to see if there was a way using roles to restrict IP addresses or even disable a user from being able to add their own ssh keys. There does not appear to be a way to do this.
My next step was to look into using VPC Service Controls. This has the ability to limit services connections to an IP range. Unfortunately I didn't not see Cloud Source Repositories in the list of services.
Is it possible that Cloud Source Repositories is a sub-service of one of the listed services in the VPC Service Controls? How would one go about making a CSR repo secure and deny access outside the facility? Please let me know if there are any other solutions that I should look into or if using VPC is possible.
Cheers,
Kenny