Skip to content
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

Moving global write permissions down into the CI jobs #5370

Merged
merged 1 commit into from
Apr 17, 2024

Conversation

jkowall
Copy link
Contributor

@jkowall jkowall commented Apr 17, 2024

This attempts to solve the following issue with our security rating around token permissions on the scorecard : https://securityscorecards.dev/viewer/?uri=github.com/jaegertracing/jaeger

image

Which problem is this PR solving?

Part of #5363

Description of the changes

Moving write permissions into the jobs

How was this change tested?

It will be tested after the PR is submitted as the jobs do not fully run on my fork.

Checklist

Signed-off-by: Jonah Kowall <jkowall@kowall.net>
@jkowall jkowall requested a review from a team as a code owner April 17, 2024 19:21
@jkowall jkowall requested a review from albertteoh April 17, 2024 19:21
Copy link

codecov bot commented Apr 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.21%. Comparing base (f12d420) to head (dce89d9).
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5370      +/-   ##
==========================================
+ Coverage   95.08%   95.21%   +0.13%     
==========================================
  Files         343      343              
  Lines       16777    16781       +4     
==========================================
+ Hits        15952    15978      +26     
+ Misses        629      605      -24     
- Partials      196      198       +2     
Flag Coverage Δ
badger 10.51% <ø> (+<0.01%) ⬆️
cassandra-3.x 18.42% <ø> (-0.01%) ⬇️
cassandra-4.x 18.42% <ø> (-0.01%) ⬇️
elasticsearch-5.x 20.87% <ø> (?)
elasticsearch-6.x 20.88% <ø> (+<0.01%) ⬆️
elasticsearch-7.x 20.94% <ø> (?)
elasticsearch-8.x 21.11% <ø> (?)
grpc 14.59% <ø> (-0.01%) ⬇️
kafka 10.17% <ø> (-0.01%) ⬇️
opensearch-1.x 20.98% <ø> (+<0.01%) ⬆️
opensearch-2.x 20.98% <ø> (+<0.01%) ⬆️
unittests 91.73% <ø> (-0.03%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jkowall jkowall added the changelog:ci Change related to continuous integration / testing label Apr 17, 2024
@yurishkuro yurishkuro merged commit ceb1d25 into jaegertracing:main Apr 17, 2024
37 of 38 checks passed
@jkowall jkowall deleted the action-permissions branch April 17, 2024 20:17
varshith257 pushed a commit to varshith257/jaeger that referenced this pull request May 3, 2024
…5370)

This attempts to solve the following issue with our security rating
around token permissions on the scorecard :
https://securityscorecards.dev/viewer/?uri=github.com/jaegertracing/jaeger



![image](https://github.com/jaegertracing/jaeger/assets/1859948/512902d6-48b2-45b6-b971-a33af75dca70)

## Which problem is this PR solving?
Part of jaegertracing#5363

## Description of the changes
Moving write permissions into the jobs 

## How was this change tested?
It will be tested after the PR is submitted as the jobs do not fully run
on my fork.

## Checklist
- [x] I have read
https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
- [x] I have signed all commits
- [NA] I have added unit tests for the new functionality
- [NA] I have run lint and test steps successfully

Signed-off-by: Jonah Kowall <jkowall@kowall.net>
Signed-off-by: Vamshi Maskuri <gwcchintu@gmail.com>
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:ci Change related to continuous integration / testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants