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.
Assignment Proposal
Title
Using Bitwarden Secret Manager to centrally store, manage, and deploy secrets at scale.
Names and KTH ID
Deadline
Category
Description
In this demo we will:
In the end, we will give a brief explanation of why someone should use Bitwarden secret manager rather than the secrets in GitHub actions.
Relevance
This type of tool is very important when it comes to DevSecOps since it streamlines the process of managing secrets and deploying them at scale. It also provides a good way to integrate said secrets into Github Actions which is very useful when it comes to Continuous Integration.