Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Bitbucket Pipelines aws-lambda-deploy

Nicolas Hunter January 11, 2023

Hello Bitbucket. 
My team is currently using the  atlassian/aws-lambda-deploy image for lambda deployment.
Our lambda functions deploy but the default directory/filepath does not allow our Lambda function to run correctly. Can we change the lambda deploy function to copy only to the root directory?

/opt/atlassian/pipelines/agent/build/aws_lambda/workspace_getactivations/workspace_getactivations.py  
to 
/workspace_getactivations

 

This is the relevant snippet from the bitbucket-pipelines.yml we are using: 

- step: &BuildLambda
name: Build and package
script:
- apt-get update && apt-get install -y zip
- zip S3BucketSync.zip ${BITBUCKET_CLONE_DIR}/aws_lambda/LambdaS3Sync/S3BucketSync.py
- zip workspace_getactivations.zip ${BITBUCKET_CLONE_DIR}/aws_lambda/workspace_getactivations/workspace_getactivations.py
artifacts:
- workspace_getactivations.zip
 - step: &LambdaWorkspaceActivations
 name: Update Lambda code
 script:
 - pipe: atlassian/aws-lambda-deploy:0.2.1
 variables:
 AWS_ACCESS_KEY_ID: ${AWS_KEY}
 AWS_SECRET_ACCESS_KEY: ${AWS_SECRET}
 AWS_DEFAULT_REGION: 'us-east-1'
 FUNCTION_NAME: 'workspace_getactivations'
 COMMAND: 'update'
 ZIP_FILE: 'workspace_getactivations.zip'


1 answer

0 votes
Igor Stoyanov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 13, 2023

@Nicolas Hunter  hi. Thanks for your question.
Check this answer, is this your case?

Regards, Igor.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events