[gonzalovargas]

Creating accounts and managing billing across multiple platforms is a real pain. This is a good solution, but I’m wondering if this should be more like an open standard that platforms implement, with Stripe providing a way for platforms to charge and optionally for users to pay (in addition to credit cards, wallets like Tempo, etc)

Use cases: create accounts, set up billing, manage secrets, manage resources, get invoices/receipts

Finally, I don’t know if it’s better to use a CLI imperative approach or a more declarative one like IaC

[aledevv]

The main advantage is being able to write bash scripts that automate all provisioning operations and keep track of all the necessary commands.

My scripts typically also serve as technical documentation for specific features and they are a sort of "unique source of truth".

[steve_adams_86]

That last part struck me as well. I don't want an imperative solution, but... I'm not sure if that's just me.

Declarative solutions are perfectly fast and capable as well. They can use all the same tooling under the hood. Why choose imperative? At least I can record, validate, and version control a declarative solution. And imperative process is nice for exploration and one-off needs, but... I don't know when I'd really need that or when that's a bottleneck for me.

And I get that this is probably more of a tool for agents than humans, despite that agents are only mentioned in passing. But that's even more concerning in a way. I'm not yet comfortable with giving them tools like this.