-
Notifications
You must be signed in to change notification settings - Fork 33
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
New workflow to deploy the lambda function #261
Conversation
we should probably explain what secrets need to be added too |
Signed-off-by: Gustavo Noronha Silva <gustavo.noronha@collabora.com>
Triggered when new releases are tagged or manually. Signed-off-by: Gustavo Noronha Silva <gustavo.noronha@collabora.com>
explain where? I can add it to the doc on deploying the lambda function I guess, after it has been validated |
Signed-off-by: Santosh Mahto <santosh.mahto@collabora.com>
Signed-off-by: Santosh Mahto <santosh.mahto@collabora.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is good to go, we can't really test it until it's merged as this is an on demand workdlow.
Build the lambda function, package it as expected by AWS lambda, then update it on AWS.
For now this is only triggered manually, so that the update can be performed only when it makes sense to the developers. In the future we can make a release being tagged trigger this workflow.