Github Action to deploy a lambda from the app repository. See readme of terraform repository for detail on configuration file. You must call this action for each lambda and each datacenter. Use app-name in combination with suffix to handle multiple lambda from the same application.
[Required] Application ID to identify the apps in eks-apps. Should be identical for all resources in the same project.
Suffix for multi lambda in same repository, Default : ''
[Required] AWS role allowing Secret manager usage
Terraform version to use, Default: latest
Terragrunt version to use, Default: latest
Repository containing terraform code for secret creation, Default: FinalCAD/terraform-app-lambda
Reference to use for terraform-app-lambda repository, Default: master
Github token to avoid limit rate when pulling package
[Required] Github ssh key to pull terraform-app-lambda repository
[Required] Finalcad envrionment: production, staging, sandbox
Finalcad region: frankfurt or tokyo, Default: frankfurt
Subpath in current lambda repository to call repare_archive.sh. Only use for monorepo with multiple subdirectory and in case of Package lambda
Path to lambda configuration file, Default: .finalcad/lambda.yaml
Path to lambda policies file, Default: .finalcad/lambda-policies.json
Pull rerquest number, empty for push, will only output result in pull request without applying.
Python version to construct python zip, only for Package lambda
Dry run, will not trigger apply, Default: false
(Optional) Path where to store override content from Terraform output.
- name: Deploy lambda
uses: FinalCAD/AppLambdaAction@v1.0
with:
app-name: api1-service-api
aws-role: ${{ secrets.DEPLOY_ROLE_MASTER }}
github-ssh: ${{ secrets.GH_DEPLOY_SSH }}
environment: sandbox
region-friendly: frankfurt