-
-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to define base URL from command line. #6
Comments
I think something planned for some future release is something similar to helm where as well as a global configuration file, you can pass in single fields with a flag like # includes.ymal
variables:
baseurl: https://example.com
accesstoken: faketoken Overridden with
|
Thinking about this, it would probably have a fair bit of utility to be able to use environment variables for this purpose too, because they're well supported in most CI systems for config. |
fyi, i started to implement this here. for the time being i'm waiting for usage feedback from our developers before i add unit tests. |
@funkyfuture do you have plans to finish the branch you were working on? I had a quick look and it's looking good so far! |
phew, so, i'm currently self-assigned to tasks far away from this. afaict my team mates are still evaluating Postman. (the main showstopper to use tavern is that they need to evaluate xml responses as well, iirc they'd also prefer yaml formulated schemas to use in conjunction with Cerberus, so a plugin system for tavern seems desirable - but that's all a very different story. [though, one thought occured to me in this context and may be noted: Docker-Compose is a good example how versioned config files - having that said, feel free to merge my progress. shall i open a pr for this? |
The 'preferred' way of doing this is to use an environment variable and then put it in either a config file or the test, eg: # included.yaml
---
name: test includes
variables:
base_host: "{tavern.env_vars.BASE_HOST}"
|
Would be nice to be able to define a base URL from the command line.
The text was updated successfully, but these errors were encountered: