frodovdr/node-red
1
0
Fork 0
mirror of https://github.com/node-red/node-red.git synced 2023-10-10 13:36:53 +02:00
Code Issues Releases Wiki Activity

Updated Design: Using environment variables (markdown)

Nick O'Leary 2018-08-30 22:52:34 +01:00
parent 0878d5ce41
commit 68a7ab73c6
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Design:-Using-environment-variables.md

@ -8,9 +8,9 @@ The basic usability of the `$(ENV_VAR)` approach has issues. It can only be used
- [x] [Add envvar as option to TypedInput](#1-add-envvar-as-option-to-typedinput) (_in 0.19_)
- [ ] [Project Settings](#2-project-settings)
- [ ] [Subflow Instance Properties](#3-subflow-instance-properties)
- [x] [Compound Env Vars](#4-compound-env-vars) (_in 0.19 branch_)
- [x] [Compound Env Vars](#4-compound-env-vars) (_in 0.19_)
- [x] [JSONata support for env vars](#5-jsonata-support-for-env-vars) (_in 0.19_)
- [ ] [Function node access](#6-function-node-access)
- [x] [Function node access](#6-function-node-access) (_in dev branch for 0.20_)
### 0. Update existing env var syntax
@ -79,6 +79,8 @@ We'll add a new function to our JSONata setup to allow env vars to be retrieved:
### 6. Function node access
_In dev branch for 0.20 release_
Currently the only way to access env vars in a Function node is to either:
- import them into global context via `functionGlobalContext`