Now you've done and tested your code, it's time to send it to the cloud.
Once the user is ready to deploy their function into the cloud, call these following in the location where the file .lyrid-definition.yaml is located.
This command will zip the current folder that has .lyrid-definition.yaml file, and upload it into the platform. Once it is uploaded, the Lyrid platform will start to analyze and create different build artifacts for the modules by creating jobs in the platform.
Once the process finished, it will show you the endpoint for invoking your function.
In case of any error, user will be able to debug the error by calling our monitor function and re-running the submit function:
It should be easier for user to spot the error by using the filtering in the monitor function. See how to here.
The user can update their module in the Lyrid platform by submitting another revision of the code. Submitting another module will create a new revision that will be marked active revision. [imghr]
Only latest active revision is used for deployment and execution
User will be able to deploy their module using the following command:
- The manual deployment provides insight on errors during the deployment if an issue arises.
- To manually deploy a module to specific framework , you can use --framework "<AWS/GCP/LYR>"
- Default policy for each Cloud Platform is different, you can check the details here