Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider S3 properties on API Gateway StaticRoute #39

Open
joeduffy opened this issue May 16, 2019 · 0 comments
Open

Consider S3 properties on API Gateway StaticRoute #39

joeduffy opened this issue May 16, 2019 · 0 comments
Labels
area/providers kind/enhancement Improvements or new features

Comments

@joeduffy
Copy link
Member

The way Static Routes for API Gateway work today is convenient when I want to provision and upload S3 buckets/objects as part of the program defining the API Gateway itself. It's possible, however, that I either want to use an existing set of S3 resources, or that I'd like to provision them manually so that I can control specific properties of the S3 resources.

It would be nice if we had bucket and bucketObject properties on the StaticRoute type that would let me pass these instead of path, if I prefer using that style. This is similar to how we do the EventHandlerRoute, which can accept an inline callback if I want, but where I can always drop back to passing a Lambda object explicitly if that's what I prefer.

@joeduffy joeduffy added area/providers kind/enhancement Improvements or new features labels May 16, 2019
@danielrbradley danielrbradley transferred this issue from pulumi/pulumi-awsx May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/providers kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

2 participants