-
-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot see org/group linked secrets on repo despite having write access #4543
Comments
Are you an admin of the org? |
No, but I do have write access on this org. |
Afaik you need org admin settings to view the org's secrets. Just write is not enough. I can check that again later |
If that's how it works right now, alright but shouldn't I (even as a reader) be able to see the secrets available on a repo ? |
@zc-devs You must not be an admin of the forge nor the organisation |
Sure.
The members of
Therefore, I believe this perfectly matches the requirements
And if we are going to analyze this sentence ⬆️ (which is kinda controversial to the previous one, BTW), then I do not have access to the repo settings (and the secrets part obviously) at all #4516 (which is right, IMO). |
Component
web-ui
Describe the bug
Hi,
I am not able to see secrets assigned to an org or groups that I am a part of in a repository where I have write access.
I can see secrets if I'm set as a Woodpecker administrator, as a regular user, I can use those secrets but the list appears empty.
I should see secrets on the settings > secrets page of a repository which I am an admin of in the forge.
To note :
When I go to settings > secrets, there is an error popping up : ": user not authorized".
The repository is placed in an organization where I have write access permissions. When I try to go back to the org by clicking on its name, the ": user not authorized" pop-up again and the list is empty.
Steps to reproduce
Expected behavior
I should be able to see secrets linked to organizations and groups that I am a part of without being a Woodpecker admin on repositories that I'm a administrator of.
System Info
Additional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]The text was updated successfully, but these errors were encountered: