Enterprise tooling (aka a usable API) and it stays out if my way.

As an ops person I disagree! Our arbitrary changes are documented in a jira ticket in the ops project. If you can’t view the ops project fill free to open a ticket in ops and we will triage it when we feel like it.

Hey now! Gitlab ci is totally fine so long as your simply running your build.sh file out of it. Anything more and your risking madness.

Just use npm to install all the dependencies. What’s the worst that can happen.

Telecos make minimal amounts on the hardware - its all in the batshit insane service costs. To give an (out of date ) example, back when ATT was getting rid of contracts I talked with some people who knew the ins and outs. On the contract model, the first 6 months paid for the device subsidy and the network, the last 18 months was pure profit. They where all super excited about the financial gains of no longer needing to do phone subsidies, but still have the customer locked in for 2+ years.

Yep c flat or b sharp. If the octave has a half step between notes (a full step is A to B, B to C, etc), then a sharp/flat is created. The octave dictates if we call it a sharp or flat, but from a mathematical perspective they are the same tone.

We’ve got it rigged up for aws sso. Each department can make any number of permissions sets (and link to any number of groups). The config for that is all stored in git (with code owners configured so you can only mess up your own stuff).

So I’m using it with Python. For me it’s able to do some stuff that terrafom never would be able to (Ive got a spot where resources are generated for each file/object on disk).

I for one am recommending pulumi for any of my teams new infrastructure needs.