Define data per request

[kyleect]

You should be able to define data on a request itself including environmental values. When parsing a request the request data object should be deep merged with parsed restfile data object.

Secrets are up in the air. How they are provided are, intentionally, outside the scope of the restfile.

id: example
data:
  userId: !!str

  local:
    userId: -1
  prod:
    userId: 1021
http: |+
  GET {{$ baseUrl}}/users/{{$ userId}} HTTP/1.1

Validation

• Can't define data for environments not defined in information.envs
• Variables with environmental values must be defined in the root of data or request.data
• Variables not defined in data must be defined in root of request.data
• Variables defined in the root of request.data can't be defined the root of data
• Can't define secrets