auth
github-actions
auth | github-actions | |
---|---|---|
13 | 7 | |
826 | 1,667 | |
2.9% | 0.7% | |
7.6 | 6.6 | |
17 days ago | 30 days ago | |
TypeScript | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
auth
-
Push code with GitHub Actions to Google Cloud’s Artifact Registry
This workflow will authenticate with Google Cloud using the Google Cloud auth GitHub Action and use Docker to authenticate and push to the registry. To make this workflow work (or flow?) we need to set up some Google Cloud resources and add in those values for our environment variables. Make sure to add in the value for PROJECT_ID where you have permission to create resources. The value for IMAGE_NAME can be anything — it’ll be created the first time this workflow runs:
-
GitHub Actions could be so much better
The issue of integration with other tools is also quite strange. Of course, this is not directly related to github actions. For example, what needs to be done to use cloud run https://github.com/google-github-actions/auth#setting-up-wor...
- you must have the "bigquery.datasets.create" permission on the selected project
-
IAM Best Practices [cheat sheet included]
While it is commonly associated with AWS, and their AWS IAM service, IAM is not limited to their platform. All cloud providers, such as Google Cloud and Azure DevOps, offer IAM solutions that allow users to access resources and systems. If you are looking for specific AWS IAM best practices, look no further than our AWS IAM Security Best Practices article:\ For the rest of this article, we will look at the generic best practices that have evolved over the last decade around each part of the basic question we started with, "who can access what?":
-
How would I use Github Actions to run a Python Script to make changes to a Google Sheets Spreadsheet?
I found this but I don't quite get how it works. I haven't done all the steps yet but I get how to set it up. I just don't understand how this just magically authenticates future steps since my code still needs a token. Should I use this to authenticate the script? If so, how do I do it and what would I need in my code? If not what should I use instead?
-
Cloud Incident Response
Cloud Identity and Access Management: This service provides fine-grained control over who has access to what resources within an organization's Google Cloud environment. It can be used to quickly revoke access to compromised accounts or limit access to sensitive resources. https://cloud.google.com/iam
-
Advanced GitHub Actions - Conditional Workflow
I use google-github-actions/auth in the first step in my job to authenticate to GCP. At this point, I have 6 different GitHub secrets to test out the concept. Each branch has two secrets with the format BRANCH_WIP and BRANCH_SA.
-
Learning Journal 3: Brainstorm a deployment process from GitHub to Google App Engine and Cloud SQL (Part 2)
There are 2 core parts authentication to GCP and App Engine deployment. Authentication is performed using auth, while a deployment uses deploy-appengine.
-
CI/CD from GitHub to Google Cloud Platform(GAE)
You should have a look at using workload identity federation and OIDC tokens. There’s a guide on https://github.com/google-github-actions/auth It means you no longer need to hardcode service account credentials in GitHub secrets anymore.
-
Learning Journal 2: Brainstorm a deployment process from GitHub to Google App Engine and Cloud SQL (Part 1)
Yes, there is a deploy-appengine action that automates the whole App Engine deployment process. Indeed, it uses gcloud commands underneath too. Either way, both approaches need an auth action to authenticate to GCP before any task can be performed.
github-actions
- On April 4, 2022 GitHub Action will force you to use "main" instead of "master" branch
-
On 2022-04-05, the default branch will be renamed from “master” to “main”
Aha: it's because the project team merged this change that intentionally fails the build when people have pinned their workflows to use the deprecated branch name: https://github.com/google-github-actions/setup-gcloud/pull/5...
(that makes sense; there has been a warning in place for a long time, and pinning to a name can be risky when the content within that reference may change over time)
-
Learning Journal 2: Brainstorm a deployment process from GitHub to Google App Engine and Cloud SQL (Part 1)
In the process of finding the answer, I discovered that the small actions are pretty much open-source. I can also go directly to their respective code repositories and learn about them. To run gsutil, I will need a setup-gcloud action.
-
Build an Uptime Monitoring System in Ruby with GCE, Cloud Storage, and PubSub
Like many aspects of the cloud, there are many ways to achieve the same result, but modern software engineering encourages CI/CD processes for several good reasons. As such, we will focus on deploying our service from Github Actions using setup-gcloud
- How to deploy Cloud Functions with GitHub Actions
-
GitOps on Kubernetes - The easy way
GKE_SA_KEY: The service account used for the project with the Base64 encoded JSON service account key. More info available here
What are some alternatives?
Aegis - A free, secure and open source app for Android to manage your 2-step verification tokens.
wait-for-jobs - Wait for the specified jobs in the same run to be complete successfully before proceeding, helpful to prestart the job
angular-auth-oidc-client - npm package for OpenID Connect, OAuth Code Flow with PKCE, Refresh tokens, Implicit Flow
devops-toolkit
google-auth-library-nodejs - 🔑 Google Auth Library for Node.js
deploy-appengine - A GitHub Action that deploys source code to Google App Engine.
act - Run your GitHub Actions locally 🚀
flow - 🌊 Continuously synchronize the systems where your data lives, to the systems where you _want_ it to live, with Estuary Flow. 🌊
azure-pipelines-agent - Azure Pipelines Agent 🚀
rubygems - Library packaging and distribution for Ruby.
harden-runner - Network egress filtering and runtime security for GitHub-hosted and self-hosted runners
blackbox_exporter - Blackbox prober exporter