-
Notifications
You must be signed in to change notification settings - Fork 34
Variables validator #86
Comments
If you don't want to handle this at runtime, maybe the most specific thing that feels like it belongs in cljs-lambda would be a task which prints out the effective config map (either for all functions, or for a specific function). You could then have a project-specific script which looks at the output of |
If it prints out effective config, per lambda function, for all functions / selected functions, it would be enough and I can handle it via another script which captures output. I'll create |
Story
Our projects heavily rely on
:cljs-lambda :defaults :env
. Also, we have production variables set in the:production
profile (profiles.clj). Sometimes we forget to ...#=(eval (System/getenv "STRIPE_API_KEY_SECRET"))
) and dev value is deployed to production,Repetitive tasks, prone to error, ... Boring, no one wants to do them.
Idea
My idea is to enhance cljs-lambda plugin with some validation task. Something like:
Do you think it's good enhancement for cljs-lambda plugin or we should create new plugin? Honestly, not sure if I can come up with generic validator, with enough parameters, to suit needs for lot of people. Our cases are described above, but there can be lot of other cases. Also not sure if plugin can read all these combinations from project & profile files without merging, etc. Didn't test it yet, just thinking aloud.
The text was updated successfully, but these errors were encountered: