Have Klotho be able to target Azure the same way it can target AWS and GCP today

when building a typical webapp it would be great to be able to have klotho keep a local folder synced with an s3/cloudfront bucket. even better if bucket-address could be retrieved at runtime from an execution unit in order to be environment specific

Currently the Map implementation of Persist is nice as it is agnostic to what Cloud storage is used. But given it is implemented in relation to the basic javascript Map object it does not have amy local storage without adding environment specific code locally. It would be very useful in a local development environment to also have persistence for this data. The only option for KVS with local storage currently in Klotho is to use Redis, however this means you are locked to using Redis in the cloud also. Suggestion is to make a Persist option that is backed locally with a simple KVS store based on some popular OSS implementation. Similarly to how Serialize is used to generalise ORM storage. The aim would be to have local storage of Key/Value at the same time as it is agnostic to what store is used on cloud.

During first usage of Klotho I followed the "Your First Kloto App" flow from documentation. What I found was that I spent a lot of extra time to get my local environment set up. Mainly related to Permissions for my AWS user. The points that would have saved me time and made experience smoother would have been: All required environment setup should be evaluated as early as possible in Klotho execution, I suggest at Klotho compile time or somewhere very early in deployment steps in order to not waste time: * Check that aws can authenticate (Maybe just do an "aws get-user"?) * Check that docker deamon is running and can connect to socket (This happens very late in Pulumi build script, so it takes a lot of time before the warning arrives. That time is wasted if docker is not setup) * Explicitly list all Policy's the AWS user should have permissions for at compile time. Use the exact name of the policy as shown in AWS IAM interface. (This warning is not shown until latest point in Pulumi-script so it takes a lot of iterations to get all the correct permissions set up, the errors in Pulumi do not say the exact permissions Policy to use. I hate working with permissions on the various cloud providers interfaces...)

it would be nice if klotho automatically handled all parts of attaching domains without any manual steps either in aws console or klotho configuration. assuming the domain has a zone on aws (or whatever infrastructure) maybe adding a "domain=sub.domain.com" on expose annotation and klotho would magically solve all requires steps

The png file that is generated to show topology is very nice and I look at it quite often. I also see that it is shared in both screencasts and blog posts. You should put a Klotho reference/logo here for branding purposes, similar to how you have a one in ansi

The default output when klotho compiles is to say: "Found 1 route(s) for middleware 'mainRoute" I think it should also print the path to the route by default in order to show what it actually found and be more instructive

when compiling a klotho it seems that all folders are recursively scanned and files evaluated for relevanve to klotho's compilation. however this can lead to very long compile times when a project has large amount of irrelevant files a concrete example is a project with bootstrap where there are 1000s of assets and optinal apis. here i extract and bundle my needed assets as part of build script, but still want to keep full set of assets in same project/repository. so i would like to explicitly tell klotho to not care about that folder in order to keep compile times down

Api gateway on aws does not support http, it would be great if klotho automatically set up the a cloudfront distribution that handles the http->https redirect for an api gateway with custom domain. This takes some googling and fiddling to figure out how to do manually

I exclusively use Cloudflare Workers these days and the rest of the Cloudflare stack. If it is sebsible for Klotho to support that, this is the feature request for it.