#245 unclear permissions and clone URL for RPMs in Pagure
Closed: Fixed with Explanation 3 months ago by ktdreyer. Opened 2 years ago by ktdreyer.

When I visit https://git.centos.org/rpms/cephadm in my browser, it's unclear that I have any permissions to this repository, or what the SSH clone URL is.

I have to discover both pieces of information from tribal knowledge (ticket #209)

On Fedora's pagure dist-git UI, I can see the list of packages to which I have access. Pagure's web UI displays the SSH clone URLs for each one.


Metadata Update from @dkirwan:
- Issue tagged with: centos-common-infra

2 years ago

Yes, that's due to Pagure not fully aware of the ACL (from pagure-dist-git package - https://pagure.io/pagure-dist-git ) through UI and so not showing that up in the UI for people member of a SIG group

That's the reason why we have documented that in the SIGGuide, that all SIG members are supposed to read before working with pagure/koji/etc ...
https://wiki.centos.org/SIGGuide#SIGGuide.2FContent.2FImport.Pushing_to_git.centos.org

Now let me tag this as a RFE, and ask pingou what he thinks of such request, but that's something that should be implemented in pagure itself first, before we can then deploy it for centos infra.

Metadata Update from @arrfab:
- Issue assigned to pingou
- Issue tagged with: doc, feature-request, need-more-info

2 years ago

Now let me tag this as a RFE, and ask pingou what he thinks of such request, but that's something that should be implemented in pagure itself first, before we can then deploy it for centos infra.

Couldn't we be able to do this via the theming no?

can you elaboratore ? as the html theme would not be able to query pagure for group membership and project and then present the git clone url for ssh ? :)
Or you meant instead just a generic line about "if you want to clone this project from rpms namespace, do <this> " ? (basically the instructions from wiki)

can you elaboratore ? as the html theme would not be able to query pagure for group membership and project and then present the git clone url for ssh ? :)

Well the html is template and there is the flask.g.fas_user.groups variable
we can access in the template.

Or you meant instead just a generic line about "if you want to clone this project from rpms namespace, do <this> " ? (basically the instructions from wiki)

That's also always an option :)

If you have an example that would automatically add the "ssh://git@git.centos.org/rpms/<project>.git" under the Clone/Source Code drop box for logged in SIG users, that would be indeed awesome !

Metadata Update from @arrfab:
- Issue marked as depending on: #456

a year ago

[backlog refinement]: Still blocked by #456

[backlog refinement]: Still blocked by #456

@ktdreyer : as pagure was migrated to a new host and so updated to pagure 5.13, can you verify if now you have other git URLs available through webui ?

I confirmed this is still a problem. When I'm logged in to the web UI, Pagure gives no indication that I have any permissions to this repository. Also it does not display any SSH url to use for cloning.

that's what I was afraid of , so clearly something for upstream pagure.
Would you mind creating a RFE upstream ?

Sure. When I write "Steps to reproduce" for this issue, what should I say for my particular privileges on this repository?

You don't have any specific permissions on that directory, because pagure-dist-git is what is used to let allow/deny push to specific branches : that's documented in the SIG guide : https://sigs.centos.org/guide/git/#pushing-to-git

So it worked for people following that doc, but clearly it's confusing that pagure Web UI doesn't reflect what pagure-dist-git does

This is confusing enough to me that I think we should just switch the Storage SIG packages to GitLab.

hi @ktdreyer : yes, I can understand ...
You can request and move projects to gitlab if you want, as it's also covered in the SIG Guide so if you want, feel free to create another ticket for this and close this one ?

Metadata Update from @ktdreyer:
- Issue close_status updated to: Fixed with Explanation
- Issue status updated to: Closed (was: Open)

3 months ago

Login to comment on this ticket.

Metadata
Boards 1