If the ENV variable CLOUD_FOUNDRY_CONFIG_PATH is defined, config files are picked up from that location. This allows components installed by the chef scripts to be run by hand. i.e. without using the wrapper vcap/dev_setup/bin/vcap_dev <start/stop> Change-Id: Ib6c971c6642bcb3b24186169e1c768ee70ba8d7b
…e install - Echo Python version installed"
This implements upload/download support on top of Net::HTTP. Originally, this was written using RestClient, however, they decided to stop streaming post bodies without telling anyone. HTTPClient was also considered, but it has bugs in its basic auth implementation. While we could work around that, I'm happier implementing the small subset of functionality that we require on top of an api that is very stable. Test plan: - Existing unit tests pass - New unit tests pass - BVTs pass locally - BVTs pass on my deployment Change-Id: Ie608b589ad4eac465a2888f28f731bcdcd9344b2
…fault, stdio would still be reopened."
…, adjusted configuration. a DB is created with minimal tables and ActiveRecord models are used to populate the database for testing."
By default, stdio would still be reopened. Refactored healthmanager functional test to decouple database access code into db_helper.rb Implemented testing for START message from HealthManager on adding an application to the Expected State. Minor stylistic changes. Change-Id: I80aeefcf6f451e6f9ae45f01d6a5338afcac62b1
This reverts commit 22e92b3. Change-Id: I2d0a03547fbffa9aa3d6122ebd7bfa81d40f4f05
…rt to attach to" This temporarily reverts commit cab9f17 to avoid our build tools triggering the new DEA build. Change-Id: Ibce8e9ccb9cd23078ee4dbbda236f1be5d42a995
This temporarily reverts commit e5c1b55 to avoid our build tools triggering the new DEA build. Change-Id: Iec9ac7a12fdbdba53c85b608535453e3c3dec61a
…push / update for an environment where there is no nginx fronting the router / cc."
…update for an environment where there is no nginx fronting the router / cc. Change-Id: I7711425c8b75ccb7b435b230c657572d2a8ffce2
…e needed to the staging gem. Change-Id: I8f5f83b2846601b35dc6929934e55ea2d24b158d
Squashed merge of satoryu:make_expiration_of_user_token_configuable: commit b3ed8ad Author: Tatsuya Sato <firstname.lastname@example.org> Date: Fri Sep 16 19:07:07 2011 +0900 Make the expiration of user token configuable The expiration of user token can be specified by editing cloud_controller.yml as follows: keys: password: 'password key goes here' token: 'token key goes here' expiration: token: 604800 # 7 * 24 * 60 * 60 (= 1 week) pid: /var/vcap/sys/run/cloudcontroller.pid rails_environment: development commit 52bf31e Author: Tatsuya Sato <email@example.com> Date: Fri Sep 16 18:11:22 2011 +0900 Add some cases of an integration test to ensure that the expiration of token can be specified. commit 916509b Author: Tatsuya Sato <firstname.lastname@example.org> Date: Thu Sep 15 14:28:09 2011 +0900 Define the interface to change the expiration of UserToken. commit 51d2a34 Author: Tatsuya Sato <email@example.com> Date: Thu Sep 15 14:27:25 2011 +0900 Refine a test case. commit 497afa4 Author: Tatsuya Sato <firstname.lastname@example.org> Date: Thu Sep 15 12:24:09 2011 +0900 Add a gem used for testing UserToken commit eb0824c Author: Tatsuya Sato <email@example.com> Date: Thu Sep 15 12:23:14 2011 +0900 Add a spec to check the expiration of UserToken can be set. Conflicts: cloud_controller/Gemfile.lock tests Change-Id: I4c5da8a826ee81de11210605e6740a3593c3a414