aws-cloudformation-res
cnab-spec
aws-cloudformation-res | cnab-spec | |
---|---|---|
1 | 8 | |
- | 939 | |
- | 0.0% | |
- | 0.0 | |
- | over 1 year ago | |
Shell | ||
- | GNU General Public License v3.0 or later |
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-res
-
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...
cnab-spec
-
No docker options
CNAB
-
Kubernetes Application Archive !! Bundle up a Kubernetes application 📦 into a single static OCI compliant archive.
Similar to https://cnab.io/ then?
-
Stronger abstraction for deployments
IMO Cloud native application bundle is what you are looking for: https://cnab.io/
-
Deployment Packaging Solutions
have you looked at CNAB ? since it uses standard OCI compliance you can have your entire application bundle on Azure registry (azure registry is OCI 2 compliant registry) and you can get more information about how to do it using ORAS cli
- Tools to Run Kubernetes Locally
-
k8s based platform
Check https://cnab.io/ and https://porter.sh/
-
Terraform 1.0 Release
I'm closely tracking an effort by Microsoft that aims to do a lot of what you're describing since I find myself bridging between these tools and deploying stacks that span tools and roles. [CNAB](https://cnab.io/) and the front-running implementation, [Porter](https://porter.sh/), enable one-step infra deployments, packaged as a single OCI-compatible container, with any number of steps, using the best tools for each of those steps. Think of using aws-cli for some initialization step (create or verify presence of a state bucket), applying some terraform to create infra, and finishing with a helm chart to complete deployment of app components. Each stage in a bundle packages not only the code to run it but also the execution binary of the tool that runs it. The spec and porter are still a moving target but it's a promising space and a nice adjacent evolution of the current state of tooling.
- Cloud Native Application Bundles Security (CNAB-SEC) 1.0.0 GA 2020
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
kapp-controller - Continuous delivery and package management for Kubernetes.
pulumi-terraform-bridge - A library allowing providers built with the Terraform Plugin SDK to be bridged into Pulumi.
helm-charts - Komodor.io public helm charts
terraform-lsp - Language Server Protocol for Terraform
kubevela - The Modern Application Platform.
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
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.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
terraform-provider-spacelift - Terraform provider to interact with Spacelift
kpt - Automate Kubernetes Configuration Editing