vinery 0.1.0

CLI tool for building modular infrastructure

vinery is the simple, batteries-included infrastructure-as-code framework that leverages opinionated, plug-and-play Terraform/OpenTofu plans to programmatically generate data and analytics infrastructure in Azure.

What vinery Is Not

❌ A state management tool.

❌ For highly specialized workloads or infrastructure needs.

❌ For teams with many platform/infrastructure/devops specialists! Don't want to make it too easy for them.

Instead, vinery Is

✅ A Terraform/OpenTofu workspace management tool!

✅ Simple! Perfect for data people and other infrastructure non-specialists!

✅ For repeatable deployments, across many tenants!

vinery comes in two parts:

• A library 📚 of plans for managing Azure infrastructure for data and analytics, that is:

  • Opinionated: reasonable choices are made for each resource, allowing for a sane amount of configuration.
  • Plug-and-play: each plan is designed to provide unique, but complementary, components to the infrastructure.

• The vine 🍃 CLI, responsible for parsing through each plan's dependencies, builds the project's plan dependency graph, and batch execution of Terraform/OpenTofu commands on the selected plans.

Simply choose which components to include from the library - vine determines the required dependencies, tells you which inputs to provide, and executes everything in sequence - allowing you (or your CI) to sit back and pour some of your vinery's best grape juice. 🍷

Getting Started

clone repo

cd vinery

pip install .

vine -h

Pre-Requisites & Disclaimers

The vine CLI expects OpenTofu CLI/Terraform CLI, as well as Azure CLI to be installed.

vinery expects no different settings or configurations than how you would normally configure the Azure provider. However, our default plans do not support inline configuration of provider credentials, since we don't recommend it ourselves.

something something

This repository supports OpenTofu and Terraform

This project was tested on:

• OpenTofu 1.9.0.
• Terraform 1.6.0.

Both are great options, but we prefer OpenTofu.

Known Bugs / Issues

• Changing an existing Databricks Workspace's public_network_access_enabled parameter via the private_frontend input variable (local.tfvars) causes the Terraform/Tofu runtime to get stuck in Still modifying.... Despite the message, if the execution is interrupted, the change is successful, as re-running the plan yields Your infrastructure matches the configuration. and the changes can be shown to have taken effect in the workspace.