chore: allow to use local cache in ec2 lambdas#297
Merged
Conversation
619c844 to
60b9b14
Compare
d9f0b90 to
56c15a7
Compare
56c15a7 to
e0e78a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds support for using locally cached EC2 runner lambda artifacts during Terraform execution.
The
download_lambdas.shhelper now checksUSE_CACHEandCACHE_PATH; when both are set and the cache path exists, it skips downloading lambda artifacts and returns the cache path to Terraform. The EC2 deployment module now uses that returned path for the webhook, runner binaries syncer, and runners lambda zip files.This also updates the tenant configuration template to use placeholders for runner user, VPC, subnet, placement, license specification, and dedicated host settings instead of hard-coded example values.
Type of Change
Checklist