Additional features

[ispyinternet]

I've been hacking your project over on my fork to get some things working as a proof of concept. Now I want to move my work over to production, and I'm either going to have to tear out the useful bits or I wonder if there is any scope to develop your repo to include the features I am looking for.

In particular, it would be nice to have a config flag that switches the CDK on or off. Just being able to build the edge server is a great feature alone, and then, as in my case, I can deploy this through my own deployment pipeline.

However, having access to the CDK deployment for development purposes is also great, but I want to be able to configure more advanced Cloudfront setups.

In my fork, I have already partitioned the CF distribution to only run the lambda edge on a certain path, however, in production, I would also like to setup an additional origin. How difficult do you think it would be to pass in a config object to define the origins / behaviours, along with specifying some of the more common options for each behavior? At least be able to specify whether to attach the CF2 and/or the Lamda@edge functions.

I know it might be asking too much. But I think the CDK switch would be very useful, at least.

[ispyinternet]

sorry, just realised you already have a deploy option which more or less turns off CDK 🤦