When I started reading the article I thought I was getting a tutorial, about the middle I realized I was getting an explanation of the intent behind a shared repository. The word misleading feels judgmental, like I’m ascribing negative intent, but I don’t think it’s that. Could use some editing, imo.

Cool demo, tho.

Interesting to see a short example of pulumi - but I think I’ll stick with opentofu/terraform.

Lots of imperative code here that generates implicit state - like teams of calls to apt.

Not clear how one would go about consolidating changes between one deployed version and updated pulumi code.

I suppose for a dev container destroy and create new is viable.

This reads like an ad for Pulumi. Please read the guidelines on self-promotion:

Self-promotion: It’s great to have authors participate in the community, but not to exploit it as a write-only tool for product announcements or driving traffic to their work. As a rule of thumb, self-promo should be less than a quarter of one’s stories and comments.

When you mant to show another tool is worse than yours, why use their configuration format & have yourself chained to their API changes? …Especially when that config is from some proprietary / corpo service. In many ways it feels like posturing a product or service to be inferior instead of having a a marshaling script to the configuration bespoke to your thing (hopefully not in JSON either).