Hey folks, quick question, which functionalities I...
# general
p
Hey folks, quick question, which functionalities I lose If I choose aws s3 as my state backend ? if there is any link, that also would be benefical
f
From the top of my head, you’ll lose the whole web console, so following the current deployment log in the web, looking up the history of deployments and details. If you want to look up data later, you’ll have to do everything through the cli and get used to navigating the json state file from
pulumi stack export
. I think the exclusive lock on the state to prevent multiple deployments colliding is also in the cloud service. You also lose the extra features of the cloud service like automation api, pulumi deployments and esc. From a cli experience, the only difference is the login process. I store my state and keys in Azure and while the transfer wasn’t great, it was doable.
f
☝️ and for a link, this is a good start to see what you lose https://www.pulumi.com/product/pulumi-cloud/
p
I'm kind of working on a workshop to give an introduction to my internal team, we are heavily using terraform/terragrunt as IaC tech. I read like almost all doc. So this is kind of crucial for me/us to answer, thanks both @full-hydrogen-5950 and @future-hairdresser-70637. I will check what do we gain or lose with different type of subscriptions
👍 1
w
f
Thats true, but that’s the tier past “normal” Enterprise pricing.
f
note you can self-host with a self-managed backend but yeah that's a very self-directed thing to do 😄
@plain-vegetable-53232 if you're looking for a vs TF, check out https://www.pulumi.com/docs/concepts/vs/terraform/ if you haven't seen it. there is good interop with pulumi there too - e.g. reading TF state and working alongside TF/TG, importing TF, etc
🙌 1
f
Have I missed something? Can you self host without paying for Business Critical license? Or are we talking about hosting just the state?
f
Self-hosting is available in the Pulumi Business Critical edition and when using the open source, self-managed backends.
but yeah, I wouldn't recommend the latter, personally/professionally? 😄
f
Right, it’s a bit fuzzy in the terminology. The open source self managed backends are:
a manually managed object store, including AWS S3, Azure Blob Storage, Google Cloud Storage, any AWS S3 compatible server such as Minio or Ceph, or your local filesystem
f
hold up, sorry you're right and the wording is confusing
i get tripped up on this from time to time - the and needs to be bolded imo 😄
f
I’d host my own backend if it gives me the web console, but there isn’t any budget
I have a mini-clone though that I wrote as a hobby project to play around with devcontainers and testcontainers
f
nice! yeah, there's a lot of work that's gone into (and is going into) Pulumi Cloud. That's a decent part of what you're paying for.
f
Yeah, I loved the web console, but the pricing model is just such a poor match for our setup. Our test stack is currently ~1000 resources and isn’t fully complete. As I move the setup into private network, I expect it to roughly double due to how Azure is setup. The offer I got for enterprise with sufficient resources was out of our league.
I guess it’s worth mentioning that a majority of our resources aren’t hosts, containers and databases, but permissions, identities, rules and the massive amount of linking resources needed in Azure that don’t cost money in the cloud.
🤔 1
p
@full-hydrogen-5950 I see your point, so that's why you prefer to store your state at not pulumi cloud but somewhere at s3 etc.
Yea I will need to check and talk with the pulumi team regarding that part,
f
Yeah. I massively would have preferred to use Pulumi Cloud, but it just wasn’t doable for us. We also want SSO which made things even worse since it pushed us into Enterprise feature set.
p
Thanks, your comments were insightful 🙂 @full-hydrogen-5950
👍 1