8000 [meshery/meshkit] Prepare workflows for moving from default "write" to default "read" permission · Issue #705 · meshery/meshkit · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[meshery/meshkit] Prepare workflows for moving from default "write" to default "read" permission #705

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.

Sign up for GitHub

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

Jump to bottom
Open
sangramrath opened this issue Apr 2, 2025 · 2 comments
Open

[meshery/meshkit] Prepare workflows for moving from default "write" to default "read" permission #705

sangramrath opened this issue Apr 2, 2025 · 2 comments
Labels
security

Comments

@sangramrath
Copy link
Contributor

Current Behavior

The workflows and the job(s) in them default to 'write' permissions set at the repository. Permissions for the GITHUB_TOKEN is not set individually at the workflow level.

Desired Behavior

Workflows permissions should default to 'read' and GITHUB_TOKEN permissions should be modified in workflow files to use privileged permissions as required.

Implementation

Acceptance Tests

Contributor Guides and Handbook
@sangramrath sangramrath converted this from a draft issue Apr 2, 2025
@welcome Welcome
Copy link
welcome bot commented Apr 2, 2025

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.

@Sumitsh28
Copy link

I have made the necessary modifications in workflow files. Can I raise a PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
security
Projects
KubeCon EU 2025 Security Slam
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sangramrath @Sumitsh28
0