-
Notifications
You must be signed in to change notification settings - Fork 67
Configuration Process for Internal Developers
In the public repo, you will notice that Bluepic-Server/cloud_config.json, Bluepic-Server/properties.json, Bluepic-OpenWhisk/local.env, and a few other files are pretty empty. To populate those with the values we use for testing internally, follow these steps:
-
Clone the Testing Credentials repo:
git clone https://github.com/IBM-Swift/Testing-Credentials.git -
Next, clone the DevOps repo:
git clone https://github.com/IBM-Swift/DevOps.git -
Now navigate to the
/DevOps/scripts_assets/gradle_assets/build-deploy-assets/directory, on your local machine, where thecopy-project-properties.gradlescript is. -
Make sure you have Gradle installed, if not, you can install it like this with Homebrew:
brew install gradle -
Now, you simply run the script with the appropriate parameters. If you get Permission denied errors after running the script, you main have to run the below command with
sudo. Here is an outline:gradle copyProperties -b copy-project-properties.gradle -PappOpenSourceFolder=<Testing-Credentials-Root-Directory>/BluePic/development -PappRootFolder=<Bluepic-Root-Directory>This script simply copies the files from
-PappOpenSourceFolderand puts them in-PappRootFolder, overwriting if necessary and retaining the directory structure. Afterwards, the configuration files;Bluepic-Server/cloud_config.json,Bluepic-Server/properties.json, andBluepic-OpenWhisk/local.envshould be populated with valid credentials and will be untracked by git so we don't accidentally commit them to the remote repo.