chore: use team scoped context instead of org scoped context #4612
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
now that it is part of go.mod we don't have to manually download it anymore
PS: Why isn't this signed..? Co-authored-by: dotkas <kaspar.moss@snyk.io> Co-authored-by: alina-ilie <alina.ilie@snyk.io>
85ae1ad to
5391ed3
Compare
PeterSchafer
approved these changes
May 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR updates the contexts being used in our CircleCI deployment. We are following least privileged policies and switching to team scoped tokens.
How should this be manually tested?
The deployment pipelines should be successful as before, no code changes were made
Any background context you want to provide?
This change was made to follow ProdSec Standards & Procedures
What are the relevant tickets?
HEAD-300