Congratulations on your release Please don't mandate the use of static AWS credentials; the aws sdk is capable of abstracting away all those gory details for y

Congratulations on your release Please don't mandate the use of static AWS credentials; the aws sdk is capable of abstracting away all those gory details for you, including allowing someone to use those env-vars if they really want, but forcing them is a headache for an organization that uses AssumeRole (or its friends) for everything: https://github.com/eleven-sh/cli/blob/v0.0.4/internal/cloudproviders/aws/errors_presenter.go#L60 https://github.com/eleven-sh/cli/blob/v0.0.4/internal/cloudp... I wasn't readily able to find the Route53 logic; how are those "serve --as" domains created/updated?