Hi there 👋

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

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

It would be nice to directly deploy from the Klotho CLI instead of using Pulumi or Terraform. But it doesn't mean you cannot use Pulumi or Terraform. They provide an API.

Authentication/Authorization is pretty painful in AWS with Cognito. Would be nice to see some sort of auth directive to be able to set up authentication with an API Gateway (or whatever the other non-AWS cloud equivalents are). Admittedly this is a pretty tall order, but placing

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.

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

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

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

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

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 a