canvas-lms/spec/support
Ethan Vizitei ad75b72c28 make canvas pull secrets from consul, not env vars
closes CNVS-26734

distributing env vars through production is harder
than updating a shared highly available store.  We put this stuff
in consul now so it's easy to update everywhere at once.

also clean up webmock spec usage, it causes a lot of errors
because it's configuration seeps outside the specs it's currently used
in

TEST PLAN:
  1) no production changes (does not touch app code)
  2) clean install, clean config directory
  3) copy docker-compose/config/ files to your config directory
  4) you shouldn't be missing any config files when you start your
     compose file up
  5) Canvas::DynamicSettings.find("canvas") should give you a hash
      with your secrets from the init values in your config file
  6) ServicesJwt.signing_secret and ServicesJwt.encryption secret
      should pull those same values
  7) if you have env vars for ECOSYSTEM_KEY or ECOSYSTEM_SECRET, they
      should be ignored

Change-Id: I3b3c1b19d6e2a05af3e6caa2e0af6c5d1dc6df66
Reviewed-on: https://gerrit.instructure.com/71559
Tested-by: Jenkins
Reviewed-by: Simon Williams <simon@instructure.com>
Product-Review: Ethan Vizitei <evizitei@instructure.com>
QA-Review: Ethan Vizitei <evizitei@instructure.com>
2016-02-11 00:01:48 +00:00
..
onceler spec: gracefully handle sharding not initializing in specs 2015-11-06 17:11:52 +00:00
blank_slate_protection.rb spec: disallow record creation outside spec lifecycle 2015-12-11 16:36:00 +00:00
boolean_translator.rb Automatically Assign group leaders 2014-05-23 17:23:53 +00:00
jwt_env.rb make canvas pull secrets from consul, not env vars 2016-02-11 00:01:48 +00:00
sorted_by_matcher.rb Fetch grading periods for all related accounts 2015-03-24 17:41:46 +00:00