github-slack-devops-management
terraformsh
github-slack-devops-management | terraformsh | |
---|---|---|
15 | 7 | |
4 | 62 | |
- | - | |
0.9 | 3.2 | |
about 1 year ago | 29 days ago | |
Shell | ||
- | 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.
github-slack-devops-management
- [sample] GitHub-Slack integration to automatically posts messages to Slack Channel.
- Prebuilt sample: Automatically post Github notifications and messages to Slack .
-
Low-code Backends - Github samples
GitHub/Slack - Devops
- Github and Slack - DevOps Management
- Automating Github -> Slack (updates)
- This sample shows how Linx automatically post messages to Slack. Once this GitHub-Slack integration is active, the sample posts messages to Slack Channel. Post messages to Slack using Bot User for GitHub issues for a time period.
-
Monthly 'Shameless Self Promotion' thread - 2021/10
Github/Slack - posts messages to Slack Channel. Post messages to Slack using Bot User for GitHub issues for a time period.
terraformsh
-
How to avoid using symlinks for global tfvars file?
I created Terraformsh to automatically pass multiple config files in different directories so symlinks aren't needed. The idea is to use a hierarchy, so the full file path to the tfvars files in parent directories get passed on with `-var-file` options. The end result is that there aren't really "global variables", but instead just a series of variables that are split up into different hierarchies, so that any given module can use them if they need them, or ignore them if they don't need them. To differentiate potentially-conflicting variables I just give the variables unique names.
-
Keep code DRY while having hundrets of environments
It looks like we've both created the same solution! :) ltf looks very similar to terraformsh. Good luck with your project!
-
Terraformsh v0.12 released
Since people seemed to like it last time I mentioned it here, I just released another version of my Terraform wrapper, Terraformsh: https://github.com/pwillis-els/terraformsh
-
My use of Terragrunt
I noticed Terragrunt was kind of complicated, so I made this to make it easier to keep Terraform code DRY without getting complicated: https://github.com/pwillis-els/terraformsh
-
Terraform directory structure
This is similar to how I lay out my projects for use with my terraform wrapper, Terraformsh: https://github.com/pwillis-els/terraformsh/blob/main/DRY_CODE.md
- Monthly 'Shameless Self Promotion' thread - 2021/10
What are some alternatives?
realworld-api - RealWorld App backend using Linx
linux-integration - Using Linx and PuTTY, you can integrate with most Linux servers, running Commands, Scripts and Copy files to and fro.
google-drive-file-management - Simple file management between your local files and a Google Drive instance.
ltf - LTF is a minimal, transparent Terraform wrapper. It makes Terraform projects easier to work with.
github-devops-management - Generating GitHub API access tokens via OAuth 2.0. Authenticating and connecting to GitHub. Retrieve commit activities for repos. Sending email notifications from Gmail for Gitub repository commit activity for a time period
clinst - Install and manage multiple versions of command-line tools in a user's home directory
samples - List of sample applications demonstrating the ability of the Linx low-code platform.
terraplate - DRY Terraform with Go Templates
sharpspring-api - Integration template between Sharpspring marketing automation platform and Linx via REST API.
pretf - Generate Terraform code with Python
github-api-connectors - Custom built connector functions to integrate with the GitHub REST API.