Hey all, coming to you with a Lambda publishing an...
# aws
Hey all, coming to you with a Lambda publishing and versioning question! Thanks in advance for any help
Publishing the function iterates the pc config. The alias is locked to the current version of the code. Do you not want to run the new version in pc when it's published?
I do want the new version. With the question, I was trying to see if I could get the lambda version to be the same as the package behind it so that if we ever roll back the Lambda we know which version of the package we're rolling back to. For context, it's a lambda function using a docker image with a custom python package and its dependencies. Typing this out now, might just try and add that package version as a tag to the lambda function instead
Just as a followup, ended up adding package in question's version to the lambda version's description and tags. Works well enough