When running the bzt command line, does the -cloud flag need to be set in order to use the "private location"?
When I try running without my VPN connected, rather than timing out trying to access the private location machine, my tests timed out trying to hit the actual URLs under test. That suggested that the "private location" might not actually be used when -cloud wasn't specified.
Component : BLAZEMETER PERFORMANCE TESTING
This might confuse people when introduced for the first time...
The way to think of how Taurus (bzt) execute a test is one of these two ways:
Locally (BlazeMeter is not involved at all.. 1 exception is -report)
Using the BlazeMeter infrastructure (-cloud) In this case, using -cloud allows you to access every resource, including Private Locations, available to you in your BlazeMeter account.
So if you run locally (option #1) nothing from the location/cloud section will be needed