feat: initial commit for serverless operations #352
Conversation
adrianriobo
force-pushed
the
fix-166b
branch
2 times, most recently
from
2fa887b to
4c720e4
Compare
adrianriobo
force-pushed
the
fix-166b
branch
5 times, most recently
from
9af2462 to
466d60c
Compare
adrianriobo
force-pushed
the
fix-166b
branch
2 times, most recently
from
e2ddad9 to
bbddb34
Compare
adrianriobo
changed the title
|
@adrianriobo currently this PR is implementing the "scheduled destroy" operation using serverless right, or does it also run the create operation in serverless mode? |
|
Yeah, need to reduce the scope of the PR, this one creates a reusable module for AWS serverless executions and implements the destroy operation based on the timeout parameter. I will create a full epic around servlerless cause we would need to backport the functionality to Azure and define the behavior for serverless create cause for create we need somewhere to leave the credentials to connect to the target machine / service...as with serverless execution is no longer executed locally....I was thinking to create ephemeral s3 folder and create presigned urls to access assets...but we can discuss about it. |
This commit introduces a serverless module to run serverless operations on AWS, and as an example use case it introduces the timeout parameter for rhel, fedora and windows targets on AWS. When timeout parameter is set a serverless task is scheduled based on the timeout to self destroy resources created by the create operation Signed-off-by: Adrian Riobo <[email protected]>
Fix #166