Terraform/OpenTofu provider for n8n enabling Infrastructure-as-Code management of workflows, credentials, variables, and projects.
Built for Enterprise DevOps teams and infrastructure engineers managing n8n deployments at scale..
The receipts β real demand
βMy use case: Iβm building a Terraform provider to manage n8n resources (workflows, credentials, variables, projects, etc.). The goal is to automate n8n setup and deployment as part of an IaC pipeline. I think it would be beneficial to add this because: This feature would allow full integration of ...β
π Corroborated on other sources
β### Current Terraform Version <!--- Run `terraform -v` to show the version, and paste the result between the ``` marks below. This will record which version was current at the time of your feature request, to help manage the request backlog. If you're not using the latest veβ¦β
view ββ### Terraform Version Terraform v0.12.18 ### Affected Resource(s) n/a (request for new resource) In AWS EKS, clusters come "pre-configured" with several things running in the `kube-system` namespace. We need to patch those pre-configured things, while retaining any "upstβ¦β
view βWhy this is a gap
This pain showed up independently across 2 different sources β the strongest signal that demand is real and underserved.