Hacker News Reader

Comment by glenjamin | Hacker News Reader

I've spoken to an Amazon rep about this.

The best approaches they were able to suggest were:

  * Lookup config from dynamo db when the lambda runs
  * Lookup config from S3 when the lambda runs
  * Bake config into the artifacts

You can read the name of the alias you're currently running as from the context data, and use this as a key into some external system.

Not ideal.

View on HN

Suboptimal ;-). This is a common request, and we're looking at options for a config feature that's independent of the code payload. Tweet or email me detailed suggestions/asks for it: @timallenwagner or timwagne at amazon.com.

Why not inject it to `context` parameter in some variable with known name? As long as the field is exposed to CF and in the panel, it should be all we need.

Reply on news.ycombinator.com