chore: synced file(s) with cds-snc/site-reliability-engineering #56
Conversation
This file contains 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
![sre-read-write[bot]](https://avatars.githubusercontent.com/in/146819?s=60&v=4){kind=small}
sre-read-write
bot
force-pushed
the
repo-sync/site-reliability-engineering/default
branch
7 times, most recently
from
6f34def
to
1d429c9
Compare
…ols/sre_file_sync/s3-backup.yml'
…emote 'tools/sre_file_sync/export_github_data.yml'
…e 'tools/sre_file_sync/ossf-scorecard.yml'
sre-read-write
bot
force-pushed
the
repo-sync/site-reliability-engineering/default
branch
from
1d429c9
to
6bee078
Compare
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.
synced local file(s) with cds-snc/site-reliability-engineering.
SRE Workflow Sync
Description
Hello this is an automated PR from the Internal SRE Team.
This PR will sync some workflows that fill perform some important organizational requirements so that you don't have to.
Workflows being synced
The following is a list of workflows that are being synced by this action.
s3-backup.yml
This workflow will take shallow copy of the current state of your repo, zip that up and upload it to an s3 bucket in the SRE Tools AWS Account. This is a disaster recovery action that we are taking in the very slim chance that Github dissapears along with all of the copies of your repo on developer machines.
ossf-scorecard.yml
This workflow measures a set of security metrics and criteria designed to assess the security posture and practices of your repo and sends that information to Azure Sentinel.
export_github_data.yml
This workflow collects metadata about your repository and sends it to Azure Sentinel.
backstage-catalog-helper.yml
This workflow calls the Backstage Catalog Info Helper Action which is used to help teams get started with a basic Backstage catalog-info.yml file for their repository. This file is used to populate the Backstage Software Catalog and provides teams with the ability to keep track of key metadata related to their project.
Important Information
This PR should have zero impact on the functionality of your system and should be safe to merge without testing your application.
Please Note: You do not have to merge this PR if you wish to be exempt from this sync please contact internal sre through slack and we will remove your repo from the list of repos to sync. Be aware however that if you do this you will need to implement this functionality yourself.
Changed files
.github/workflows/s3-backup.ymlwith remotetools/sre_file_sync/s3-backup.yml.github/workflows/export_github_data.ymlwith remotetools/sre_file_sync/export_github_data.yml.github/workflows/ossf-scorecard.ymlwith remotetools/sre_file_sync/ossf-scorecard.ymlThis PR was created automatically by the repo-file-sync-action workflow run #11366910114