terraform-provider-github
cache
terraform-provider-github | cache | |
---|---|---|
7 | 40 | |
837 | 4,274 | |
2.2% | 1.7% | |
9.2 | 7.2 | |
7 days ago | 12 days ago | |
Go | TypeScript | |
MIT License | MIT License |
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.
terraform-provider-github
-
Github provider
There's an open feature request issue for it in the provider. I'd keep your eyes on 1534 for it to be implemented, as well as give it the 'ol thumbs-up bump.
- Is Github Actions really production ready for large corporation ?
-
The strongest principle of the blog's growth lies in the human choice to deploy it
I wanted to configure GitHub Pages using terraform because this project already uses it to configure this repository. But currently, due to how GitHub provider for terraform is written, configuring Pages requires some fiddling and will not work on the first run. During my research into how I could achieve declarative configuration for Pages, I found out that GitHub recently added actions that allow deploying to Pages without additional branch. I like this new approach better and in the future I will switch to it, but for now I decided to configure Pages manually as suggested by GitHub Pages Action that we are using.
-
Error: Failed to install provider
Someone hit the wrong switch at the factory: https://github.com/integrations/terraform-provider-github/releases/tag/v4.28.0
-
Show HN: GitHub as Code โ Manage GitHub with Terraform
Well, there are a lot of open issues [0] with no outlook to get them ever closed.
We've had issues with branch protection rules (the same code works with old actors in the state, but new actors erroring out without any reason), organization secrets, etc.
[0]: https://github.com/integrations/terraform-provider-github/is...
-
Configurable GitHub default merge action: merge, squash, rebase
https://github.com/integrations/terraform-provider-github/is...
I don't understand how this hasn't gotten more attention throughout the years. I would like to learn about why that is.
I am a big fan of Squash and Merge but it's saddening that users have to configure that by hand on a repo when they first merge a commit via the GitHub UI, as many people aren't aware or don't think about it which can lead to nasty commit histories.
Am I missing something? Am I git'ing wrong?
- How do you manage many repositories?
cache
-
GitHub Actions could be so much better
> with no persistent storage
There's https://github.com/actions/cache though?
-
Optimizing GitHub Actions Performance: Enhance Workflows with Caching
Use Cache Actions: GitHub Actions provides cache actions that simplify caching implementation. The @actions/cache JavaScript library is a popular choice for managing caching in workflows. It offers flexible options for storing and retrieving cache artifacts based on keys, scopes, and paths.
-
Speeding up GitHub Actions with npm cache
GitHub maintain a set of repos called actions. One of which is called cache.
-
How I Sliced Deployment Times to a Fraction and Achieved Lightning-Fast Deployments with GitHub Actions
By utilizing the actions/cache action action, we implemented a strategy to store and retrieve dependencies, preventing redundant installations.
-
Use GitHub Actions to Make Your GitHub Profile Dynamic
I do think it's good practice to enable caching, such that your script doesn't hit RubyGems / pip / npm / etc every time it runs.
That way at least the automation activity stays entirely within the GitHub / Azure network.
It looks like you can do that for Ruby by adding this:
https://github.com/actions/cache/blob/master/examples.md#rub...
- uses: ruby/setup-ruby@v1
-
A guide to using act with GitHub Actions
โ getting-started-with-act git:(master) act -j build WARN โ You are using Apple M1 chip and you have not specified container architecture, you might encounter issues while running act. If so, try running it with '--container-architecture linux/amd64'. โ [Node.js CI/build] ๐ Start image=node:16-buster-slim [Node.js CI/build] ๐ณ docker pull image=node:16-buster-slim platform= username= forcePull=false [Node.js CI/build] ๐ณ docker create image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] ๐ณ docker run image=node:16-buster-slim platform= entrypoint=["tail" "-f" "/dev/null"] cmd=[] [Node.js CI/build] โ git clone 'https://github.com/actions/setup-node' # ref=v3 [Node.js CI/build] โ git clone 'https://github.com/actions/cache' # ref=v3 [Node.js CI/build] โ git clone 'https://github.com/actions/upload-artifact' # ref=v3 [Node.js CI/build] โญ Run Main actions/checkout@v3 [Node.js CI/build] ๐ณ docker cp src=/Users/andrewevans/Documents/projects/getting-started-with-act/. dst=/Users/andrewevans/Documents/projects/getting-started-with-act [Node.js CI/build] โ Success - Main actions/checkout@v3 [Node.js CI/build] โญ Run Main Use Node.js 16.x [Node.js CI/build] ๐ณ docker cp src=/Users/andrewevans/.cache/act/actions-setup-node@v3/ dst=/var/run/act/actions/actions-setup-node@v3/ [Node.js CI/build] ๐ณ docker exec cmd=[node /var/run/act/actions/actions-setup-node@v3/dist/setup/index.js] user= workdir= [Node.js CI/build] ๐ฌ ::debug::isExplicit: [Node.js CI/build] ๐ฌ ::debug::explicit? false
- duplicated cache by cache action
-
runner image with MS office installed - do-able? is there a better way?
You could try to find some point in the process where you can set up Actions caches with actions/cache, otherwise Container customization for Self-Hosted Runners is currently in Beta.
-
[Question] Decrease Docker image's build time
I would configure Github Actions cache so Docker doesn't have to compile all layers from scratch every time
-
The strongest principle of the blog's growth lies in the human choice to deploy it
In the copied example, npm caching is done via actions/cache@v2 action. But we can simplify our workflow by dropping this step and using built-in functionality for caching
What are some alternatives?
git-xargs - git-xargs is a command-line tool (CLI) for making updates across multiple Github repositories with a single command.
upload-artifact
gita - Manage many git repos with sanity ไปๅฎน็ฎก็ๅคไธชgitๅบ
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
actions-hugo - GitHub Actions for Hugo โก๏ธ Setup Hugo quickly and build your site fast. Hugo extended, Hugo Modules, Linux (Ubuntu), macOS, and Windows are supported.
act - Run your GitHub Actions locally ๐
infrastructure - terragrunt infrastructure configuration
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
blog - Personal blog
setup-buildx-action - GitHub Action to set up Docker Buildx
terramate - Terramate CLI is an open-source Infrastructure as Code (IaC) orchestration tool for Terraform, OpenTofu, Terragrunt, Kubernetes, Pulumi, Cloud Formation, CDK, Azure Resource Manager (ARM), and others.
checkout - Action for checking out a repo