I know it could break some existing deployment flows, but shouldn't the lambda update-function-configuration happend before the update-function-code?
Actually the pipe atlassian/aws-lambda-deploy:0.8.0 executes the code update (along with version creation) and than it updates the function config (as seen here ). This causes the config changes not to be taken into consideration for the new version.
My current workaround is to:
1. publish the code with the expected config file using the new no-publish flag (thanks for that feature!!)
2. Republish the code, but this time it publishes a new version.
I'm not a AWS Lambda master yet, so I'm not sure if it's a misunderstanding or another way around this.
Hi, Bitbucket community! Are you a DevOps practitioner (or know one in your network)? Do you have DevOps tips, tricks, or learnings you'd like to share with the community? If so, we'd love to hea...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events