Move the creds.json file parsing to the CloudEnvironment component

[cpliakas]

The creds.json file also contains the info for the memcache servers, so it seems like the Cloud Environment class is a good place to store the credential parsing code since it is environment specific and can be reused.

[timhilliard]

@cpliakas we are looking to deprecate creds.json in favour of config.json. Both files contain the same information and are in the same folder but we would prefer config.json to be used as it is more representative of the content of the file.

[cpliakas]

@timhilliard, good to know, thanks! Would be great to maintain a grace period of one or two hosting releases where creds.json links to config.json once the change happens. I know there are people not using the SDK who have this hard-coded, so I want to make sure they have time to transition.

[timhilliard]

There are no plans to remove it anytime soon so you don't have to worry. We
just may not add extra functionality to it. That will go into config.json.

On Sun, Mar 16, 2014 at 11:06 PM, Chris Pliakas notifications@github.comwrote:

@timhilliard https://github.com/timhilliard, good to know, thanks!
Would be great to maintain a grace period of one or two hosting releases
where creds.json links to config.json once the change happens. I know there
are people not using the SDK who have this hard-coded, so I want to make
sure they have time to transition.

Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-37756559
.

Tim Hilliard

Cloud Hosting Engineer | Acquia http://acquia.com/

tim.hilliard@acquia.com | @big_bear84 https://twitter.com/big_bear84

[cpliakas]

Added issue to track "credentials" vs "config" nomenclature change.