-
Notifications
You must be signed in to change notification settings - Fork 3k
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
--config command line argument #1359
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1359 +/- ##
==========================================
- Coverage 80.74% 80.15% -0.60%
==========================================
Files 24 24
Lines 2254 2212 -42
Branches 345 345
==========================================
- Hits 1820 1773 -47
- Misses 343 346 +3
- Partials 91 93 +2
Continue to review full report at Codecov.
|
On further testing I've discovered you currently can't use a specified conf file to set the locustfile, because that's handled by the Since that parser is currently given the |
Makes sense! Everything else looks about the PR looks good to me! |
Yep! The reason we're going through some hoops with the Otherwise I think this PR looks good! What one could do is to add code for generating a table of all available configuration options that is automatically run when the docs are built. We have such table for all the environment variables, and the code that generates it can be seen here: Lines 27 to 57 in 6f80d63
The generated table is then included into the Configuration documentation page here: Line 29 in 6f80d63
|
Now merged! Thanks! I changed the table with all available environment variables, to also include the configuration file setting keys. (e40edfe) |
This PR adds a
--config
command line argument to locust.Fixes #1334
Includes tests and updates to docs.
The help text for the argument is a bit terse, I'd be happy to change that to something better.