Assigned
Status Update
No update yet.
Comments
de...@northwell.edu
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.
ku...@google.com
ku...@google.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.
Description
Issue summary: get IAM policy for repo by SDK and API behaves different from the console repo permission.
It seems gcloud source repos get-iam-policy command and its API both only return all roles granted directly to specific repo without showing those inherited by the specific repo.
Also based on the api or gcloud naming, it sounds like it should return all roles in a specific source.