Ringo De SmetNew Release: #Pulumi provider for Scaleway v1.50.1
https://github.com/pulumiverse/pulumi-scaleway/releases/tag/v1.50.1
JAVAPROStop debugging broken YAML deployments at 2am. Wladi Mitzel shows how Java teams can define, test & deploy cloud infrastructure with real #Java code instead of YAML chaos — with #JUnit, refactoring, #CI/CD & type safety: https://javapro.io/2026/05/12/stop-writing-yaml-how-to-define-test-and-deploy-your-cloud-in-pure-java/
New Release: #Pulumi provider for Grafana v2.32.0
https://github.com/pulumiverse/pulumi-grafana/releases/tag/v2.32.0
New Release: #Pulumi provider for Grafana v2.31.0
https://github.com/pulumiverse/pulumi-grafana/releases/tag/v2.31.0
Adrian 🔹currently investigating a good directory structure for my #IaC with #pulumi
there will be my "www stuff", but i also want to leave some space for silly side projects. so maybe some sort of multi-project setup ?
not sure yet! but reading through this as a start https://www.pulumi.com/docs/iac/guides/basics/organizing-projects-stacks/
Nebraska.CodeInfrastructure as Code isn't a single tool - it's an ecosystem of approaches and tradeoffs.
At Nebraska.Code(), Mike Benkovich shares how these popular Azure infrastructure tools compare and when each is the right choice for your environment.
🔗 https://nebraskacode.amegala.com/
#NebraskaCode #Azure #Terraform #InfrastructureAsCode #Pulumi #Bicep
farcallerI think I actually figured the sweet spot:
1. Author #routeros config in #nix.
It just makes sense. It's declarative but with good options, and I can model all of my routers and cross-reference the configuration with Nix modules support. The options hierarchy loosely follows Mikrotik, the modules offer logical slicing.
2. Nix outputs JSON.
As JSON is a valid YAML, this can be fed straight into Pulumi’s YAML SDK. Even better, #pulumi calls Nix itself!
3. Pulumi actuates the state.
This solves the problem of secrets in Nix (no secrets), the diff calculation (3-way sync between plan, state, live), and tolerance to manual router config changes that I might forget about.
4. A script runs Pulumi up and does a real diff.
Everything above is vibecoded, so this is the guardrail: even if Pulumi provider fucks up, the script will show the real diff between the live config export before and after. It's not a state diff, it's a semantic diff of routeros export, and it's 100% reliable in telling what did actually change.
New Release: #Pulumi provider for Scaleway v1.50.0
https://github.com/pulumiverse/pulumi-scaleway/releases/tag/v1.50.0
New Release: #Pulumi provider for Grafana v2.30.1
https://github.com/pulumiverse/pulumi-grafana/releases/tag/v2.30.1
Most Infrastructure-as-Code breaks once complexity appears: copy-pasted #YAML, hidden dependencies & untestable configs. @wlami shows how #Java replaces fragile cloud configs with reusable, testable infrastructure components: https://javapro.io/2026/05/12/stop-writing-yaml-how-to-define-test-and-deploy-your-cloud-in-pure-java/
