Feature Request: Collection Environment Variable Interpolation

[janrito]

practices around API authentication, token handling, etc vary widely. It would be really useful to be able to interpolate an environmental variable in a collection file. E.g.

# file: .envrc
$API_TOKEN="super-secret-token"

# file: api.posting.yaml
name: Make an API Request
method: POST
url: https://bad-api.org/api/v1/list
params:
  - name: apiKey
    value: $API_TOKEN

[darrenburns]

This is coming in the future, but will take a bit of work for it to integrate nicely with syntax highlighting in the request body text area.

[darrenburns]

@janrito I've got an initial implementation of this in the latest version. See the docs here for more details. It's a first pass - there's no autocompletion or highlighting of invalid variables etc yet)

The syntax is slightly more verbose than your suggestion as I still need to determine whether the .env file approach is "enough". In the near future I may drop the requirement to write $env: and instead just have $, but I need to think things through a bit first :)

(Also let me know if you have any feedback!)

[janrito]

Amazing, this works perfect for me.

It took me a little to understand that I had to also set POSTING_USE_HOST_ENVIRONMENT=true in order to use direnv defined variables.

This is exactly what I needed. Thanks for the quick update!

[darrenburns]

No worries - you can also set use_host_environment: true inside your config.yaml if that's easier for you.

[glennbach]

the link for the docs isn't working for me. i was trying something like:

`headers:

• name: Authorization
  value: ${env:TEST_API_TOKEN}
  `

or
`headers:

• name: Authorization
  value: Token ${env:TEST_API_TOKEN}
  `

and I just get errors.

Thanks

[glennbach]

nevermind. it doesn't need the env:, and i was misunderstanding something else.