Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by
Title
w
wonderful-action-5267
09/29/2021, 1:08 AM
Hey all, started using Pulumi at work for setting up our AWS infrastructure (mainly API's and lambda functions) and it's been a joy so far! We've gotten to a point where we're adding provisioned concurrency to a lambda function following the example here:
https://github.com/pulumi/examples/blob/258d3bad0a00020704743e37911c51be63c06bb4/aws-py-serverless-raw/__main__.py#L94
I figured out how to actually publish the function using the
publish input argument
so that there's a
published version for the Provisioned Concurrency Config
and noticed that the versions start at 1. The lambda contains a custom python package with a SEMVER version. If I wanted to tag the lambda version to that SEMVER value instead, is there a way to feed in that value along with the
publish
argument? Or is this a use case for creating lambda aliases with that SEMVER value instead?
Ah sorry, meant to post this in
#aws
#python
Join Slack