pi-remote | Interface for remote control via pi

Assuming you're using install.sh as an init action for Dataproc, your export commands would only export those environment variables in the local shell session running the init action, not persistently for all Spark processes that run thereafter.

The way to have Spark use custom environment variables is to add them to /etc/spark/conf/spark-env.sh. Here's a spark user discussion about how to set java.library.path in Spark.

Essentially you can just use a heredoc in your init action around the parts that export environment variables. However, as shown in https://issues.apache.org/jira/browse/SPARK-1719 the environment variable won't be sufficient to propagate the library path into the executors in YARN; spark explicitly sets the library path rather than propagating through LD_LIBRARY_PATH, so we must use spark.executor.extraLibraryPath as well in spark-defaults.conf

We were using an old version of pip, 1.5.6, which came out in May 2014. When we specified the index-url on the command-line sudo -E pip install --index-url https://username:password@artifactory.myorg.com/artifactory/api/pypi/pypi-remote/simple --ignore-installed pip setuptools wheel everything worked as expected so we're assuming that this old version of pip does not use pip.conf or, if it does, it doesn't use it in the same way.

Once that command (which upgrades pip) completed successfully subsequent calls to pip in the same script did not require --index-url specifying because they used pip.conf as expected.

Try requiring rails_helper instead of spec_helper, see How is spec/rails_helper.rb different from spec/spec_helper.rb? Do I need it?

rails_helper should require File.expand_path("../../config/environment", __FILE__) then config/environment should call Rails.application.initialize! and that should be loading initalizers/active_admin.rb and defining Admin::InactiveUserController before your test starts.

After initializers/active_admin has run you should be able to inspect ActiveAdmin.application.namespaces.map(&:name), which in your case should be [:admin]. If so then inspect ActiveAdmin.application.namespaces[:admin].resources.map(&:c‌​ontroller) which should give you the list of controllers that have been created.