I'd like to be able to ask pants to go "offline" entirely. This would stop any efforts to make HTTP or other network requests (instead complaining that it's offline), and would need to be paired with a "go offline" command that predownloads all sorts of things that might be necessary to run offline. An example of such a use case would be working on a plane or in a secure environment that intentionally doesn't allow network access. I see a ton of options on http://www.pantsbuild.org/options_reference.html which would allow me to prevent individual tools (like e.g., ivy) from talking to the internet (by specifying a bad proxy, for example) but haven't seen anything obvious to ask the entire pants ecosystem to stay offline. Am I missing something?
I'd like to be able to ask pants to go "offline" entirely. This would stop any efforts to make HTTP or other network requests (instead complaining that it's offline), and would need to be paired with a "go offline" command that predownloads all sorts of things that might be necessary to run offline. An example of such a use case would be working on a plane or in a secure environment that intentionally doesn't allow network access. I see a ton of options on http://www.pantsbuild.org/options_reference.html which would allow me to prevent individual tools (like e.g., ivy) from talking to the internet (by specifying a bad proxy, for example) but haven't seen anything obvious to ask the entire pants ecosystem to stay offline. Am I missing something?