Hi! Honest question, why did decide on using pulomi instead of just using the boto3 Python library to interact with aws? Feels like it adds a lot of overhead where something like boto3 could just be abstracted away?
1. state management & stages - pulumi already deals with state and has support for stages (stacks) which stelvio will need.
2. there are things outside of AWS that stelvio might support later (cloudflare, etc.)
Initially I was gonna use AWS CDK which I use at work but Pulumi seems to have faster deployment and option to use other things than AWS. (Although AWS is main focus of Stelvio at leats for now)
Comments
Hi! Honest question, why did decide on using pulomi instead of just using the boto3 Python library to interact with aws? Feels like it adds a lot of overhead where something like boto3 could just be abstracted away?
Hi! Good question, few reasons:
1. state management & stages - pulumi already deals with state and has support for stages (stacks) which stelvio will need.
2. there are things outside of AWS that stelvio might support later (cloudflare, etc.)
Initially I was gonna use AWS CDK which I use at work but Pulumi seems to have faster deployment and option to use other things than AWS. (Although AWS is main focus of Stelvio at leats for now)