3 ms·
Why aren't you using aliases[1] for denoting dev, prod, etc? [1] http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html http://docs.aws.amazon.com
by adjohn 10y ago
Why aren't you using aliases[1] for denoting dev, prod, etc?
[1] http://docs.aws.amazon.com/lambda/latest/dg/versioning-aliases.html http://docs.aws.amazon.com/lambda/latest/dg/versioning-alias...
- djhworld 10y agoThis was before AWS introduced aliases and versioning, think back to summer 2015. Aliases are still a half solution to this problem though, you would still need logic in your code to say "if alias == PROD then ... else ..." for configuration, something I'd rather do without. EDIT: by configuration I mean configuration that's specific to an environment. Imagine you had a Lambda that wrote data to an S3 bucket, you wouldn't want to accidentally mix TEST/LIVE data in the same location, so you would use a configuration property to inform the Lambda where to write.
- adjohn 10y agoThanks for the explanation, that makes sense. We wanted to see aliases as well, because it's cumbersome setting a client ID for our Lambda monitoring service.