Handle environment variables in YAML config files
See original GitHub issueIt would be a really great feature to have the base URL be separate from the URL of the test. The main use case for this is in having a single config file that you want to run on multiple environments of a site. In my config file, I’d like to be able to say:
url: /my-page
Then on the command line, be able to set the base with something like:
phantomas --config=my-config.yaml --base-url=http://foo.com
Is this implemented, or possible? I’m happy to help out with a PR here, but I’m not sure where to start.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to use a YAML file or environment variables to populate ...
In most cases, we suggest using a config variables YAML file. YAML files make variables more visible, easily editable, and allow for modularization...
Read more >Use environment variables in the configuration - Elastic
You can use environment variable references in the config file to set values that need to be configurable during deployment. To do this,...
Read more >Environmentalize your YAML configuration
Enable environmentalization. To enable environmentalization, create a file named values.yaml in the root directory where your YAML entity store is located. The ...
Read more >Python YAML configuration with environment variables parsing
Load a YAML configuration file and resolve any environment variables Note: ... Python YAML configuration with environment variables parsing.
Read more >Document how to use environment variables in `.yml` config file
yml ) to use graphql-codegen on a CI server. Describe the solution you'd like. Be able to pass headers in via the CLI,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, just realized if this was supported for various configuration keys in the config file, it would also provide a way to change the report type on the fly too. Sweetness!
https://www.npmjs.com/package/optimist-config-file