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.
I had to delete the folder instead of just the file to get it to work.
rm -rf /opt/atlassian/pipelines/agent/build/.bitbucket/pipelines/generated/pipeline/pipes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lucas, glad you fixed it!
It would be great if you could share your solution with the rest of the Community, in case anyone encounters something similar.
Have a good day :)
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.