aws-cloudformation-resource-providers-rds
mazzle-starter
| aws-cloudformation-resource-providers-rds | mazzle-starter | |
|---|---|---|
| 1 | 3 | |
| 25 | 9 | |
| - | - | |
| 8.2 | 3.4 | |
| 8 days ago | 8 months ago | |
| Java | HCL | |
| 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.
aws-cloudformation-resource-providers-rds
-
Terraform 1.0 Release
Merely as the technical answer to your question, not as advocacy: CFN has custom providers [0] and they've started publishing quite a few implementations on GH (but I haven't tried them to know if they're for real): e.g. https://github.com/aws-cloudformation/aws-cloudformation-res...
As far as I know, it is possible to bridge terraform providers into a CFN stack using that mechanism, similar to how Pulumi works
0: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGui...
mazzle-starter
-
Scaling Relational SQL Databases
I take advantage of I/O being parallel in Python in my mazzle continuous integration pipeline tool. I'm not sharing mutable state.
I spin up a graph of python Threads and each joins others in a graph. This way we can run graphs in parallel. See this graph - the parts that look like this:
dependency -> {parallel1; parallel2; parallel3} -> postparallel
parallel1, parallel2, parallel3 can run in parallel in a separate python thread because the IO is parallel.
postparallel joins parallel1, parallel2, parallel3 and waits for them all to complete.
Where parallel1-3 is things like ansible, packer (slow), AMI builds, chef runs etc.
https://github.com/samsquire/mazzle-starter/blob/master/arch...
- Terraform v1.0 Is Out
-
Terraform 1.0 Release
I use a tool I wrote to layer my infrastructure with layers called components and I configure it with a Graphviz file.
My tool, called mazzle (previously devops-pipeline) would run parts of the graph that can run in parallel in parallel. It can also run parts of the build on SSH workers. You bring up the workers at the beginning of the build.
Here's an example of a graph generated from graphviz file: https://github.com/samsquire/mazzle/blob/master/docs/archite...
This graph brings up a hashicorp vault server, Java application, bastion proxy etc.
here's the graphviz file: https://github.com/samsquire/mazzle-starter/blob/master/arch...
It describes the ordering of the infrastructure, the invocation of Ansible, packer, shell scripts to set up vault etc.
The idea is to be able to bring up a new environment by changing one parameter. There's a React GUI too.
https://devops-pipeline.com
What are some alternatives?
cue - CUE has moved to https://github.com/cue-lang/cue
dhall-terraform - Generate dhall records from terraform resouces, data_sources & providers
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
aws-cloudformation-res
pulumi-provider-boilerplate - Boilerplate showing how to create a native Pulumi provider
terraform-ls - Terraform Language Server
pulumi-provider-boilerplat
pulumi-tf-provider-boilerplate - Boilerplate code for Terraform provider-backed Pulumi packages
porter - Porter enables you to package your application artifact, client tools, configuration and deployment logic together as an installer that you can distribute, and install with a single command.