-
Notifications
You must be signed in to change notification settings - Fork 112
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
Feature Request: Allow constructs to be delivered via custom Serverless Plugin(s) #104
Comments
Thanks for your suggestion! Have you seen this? #52 |
Oh Yeah, this bit of the thread :-) - #52 (comment) Do you have a roadmap for this at all and how can I assist? |
Closing this particular Feature Request Issue since duplicates #52. |
@walmsles thank you for this issue, this is EXACTLY the kind of problem we'd like to solve eventually.
Yes! We're exploring some ideas with Lift, and also eventually with the Serverless Framework to provide a solution for these use cases. I'm taking good note of your use case, thanks again. |
I love the idea of this project and would like to make use of it as a Serverless Blueprint delivery mechanism. I am growing Serverless build teams at the moment and being able to deliver blueprints pre-packaged like this is really beneficial.
My proposal is to enable Serverless plugin hooks for the Construct Provider load so that I can use the pre-packaged constructs in Lift OR I can replace the included with my own developed Construct Provider(s) so I can control the blueprints we share OR add my own to the pre-packaged list - I feel both scerarios make sense - Add more constructs of my own or Replace the constructs altogether.
In this way, I could build my own serverless plugin to add my own production-ready constructs built to my Corporate Cloud requirements for security and Least privilege access.
Happy to work on adding this in if you want but wanted to Create this feature request first to understand your current roadmap and whether this is a direction you are planning to head and makes sense for this project.
Happy to discuss offline too if you wanted to chat about it in more detail.
The text was updated successfully, but these errors were encountered: