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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,148
Community Members
 
Community Events
176
Community Groups

Bitbucket Pipelines aws-lambda-deploy

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

@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

Atlassian Community Events