You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I use atlassian/aws-lambda-deploy as pipe to deploy code to AWS Lambda, I have 2 environments , and they are dev and production. However, after deploying to dev successfully, and going to production deployment, it fails at step update-lambda.sh whereas I believe the code deployed successfully to production, it just marks the status failed due to lacking permission to write artifacts files
There is a work around solution that we need to run this command at the end of each lambda deployment step (except the last one) to clean the artifacts data
rm -rf /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes/aws-lambda-deploy-env
Hopefully, the team will fix this problem soon by upgrading the image.