Merge branch 'develop'

# Conflicts:
#	README.md
#	TopcoderXDeploy.md
#	configuration.md
#	package-lock.json
#	package.json
#	src/app.js
#	src/common/constants.js
#	src/common/helper.js
#	src/config.js
#	src/controllers/CopilotPaymentController.js
#	src/controllers/IssueController.js
#	src/controllers/ProjectController.js
#	src/front/src/app/add-copilot-payment/add-copilot-payment-controller.js
#	src/front/src/app/add-copilot-payment/add-copilot-payment.html
#	src/front/src/app/copilot-payments/copilot-payment.service.js
#	src/front/src/app/copilot-payments/copilot-payments-controller.js
#	src/front/src/app/copilot-payments/copilot-payments.html
#	src/front/src/app/helper.js
#	src/front/src/app/less/custom.less
#	src/front/src/app/main/issue.service.js
#	src/front/src/app/main/main.controller.js
#	src/front/src/app/main/main.html
#	src/front/src/app/upsertproject/transfer-ownership-dialog.controller.js
#	src/front/src/app/upsertproject/upsertproject.controller.js
#	src/front/src/app/upsertproject/upsertproject.html
#	src/front/src/components/common/navigation.controller.js
#	src/models/CopilotPayment.js
#	src/models/Issue.js
#	src/models/Project.js
#	src/routes.js
#	src/services/AppHealthService.js
#	src/services/CopilotPaymentService.js
#	src/services/GithubService.js
#	src/services/IssueService.js
#	src/services/ProjectService.js

Author: jmgasper

.DS_Store

@@ -0,0 +1,78 @@
+version: 2
+defaults: &defaults
+    docker:
+      - image: circleci/python:2.7-stretch-browsers
+install_dependency: &install_dependency
+  name: Installation of build and deployment dependencies.
+  command: |
+    sudo apt install jq
+    sudo pip install awscli --upgrade
+    sudo pip install docker-compose
+install_deploysuite: &install_deploysuite
+  name: Installation of install_deploysuite.
+  command: |
+    git clone --branch v1.4.1 https://github.com/topcoder-platform/tc-deploy-scripts ../buildscript
+    cp ./../buildscript/master_deploy.sh .
+    cp ./../buildscript/buildenv.sh .
+    cp ./../buildscript/awsconfiguration.sh .
+restore_cache_settings_for_build: &restore_cache_settings_for_build
+  key: docker-node-modules-{{ checksum "package-lock.json" }}
+
+save_cache_settings: &save_cache_settings
+  key: docker-node-modules-{{ checksum "package-lock.json" }}
+  paths:
+    - node_modules
+
+builddeploy_steps: &builddeploy_steps
+      - checkout
+      - setup_remote_docker
+      - run: *install_dependency
+      - run: *install_deploysuite
+      - restore_cache: *restore_cache_settings_for_build
+      - run: ./build.sh
+      - save_cache: *save_cache_settings
+      - deploy:
+          name: Running MasterScript.
+          command: |
+            ./awsconfiguration.sh $DEPLOY_ENV
+            source awsenvconf
+            ./buildenv.sh -e $DEPLOY_ENV -b ${DEPLOY_ENV}-${APPNAME}-deployvar
+            source buildenvvar
+            ./master_deploy.sh -d ECS -e $DEPLOY_ENV -t latest -s ${DEPLOY_ENV}-global-appvar,${DEPLOY_ENV}-${APPNAME}-appvar -i ${APPNAME}
+
+
+jobs:
+  # Build & Deploy against development backend
+  "build-dev":
+    <<: *defaults
+    environment:
+      DEPLOY_ENV: "dev"
+      APPNAME: "topcoder-x-ui"    
+    steps: *builddeploy_steps
+
+  "build-prod":
+    <<: *defaults
+    environment:
+      DEPLOY_ENV: "prod"    
+      APPNAME: "topcoder-x-ui"  
+    steps: *builddeploy_steps
+
+workflows:
+  version: 2
+  build:
+    jobs:
+      # Development builds are executed on "develop" branch only.
+      - "build-dev":
+          context : org-global
+          filters:
+            branches:
+              only:
+                - develop
+
+      # Production builds are exectuted only on tagged commits to the
+      # master branch.
+      - "build-prod":
+          context : org-global
+          filters:
+            branches:
+              only: master

.circleci/config.yml

@@ -0,0 +1,40 @@
+## Migrate the data to Dynamo
+
+Prerequisite is to turn off any throttling on the DynamoDB, temporarily
+
+1.  Download the migration-tools.zip from here:  https://github.com/topcoder-platform/topcoder-x-ui/issues/140#issuecomment-497663806
+2.  Unzip
+3.  Modify `migration-tools/config/default.js` to match prod
+  * MONGODB_URL: Will provide in Slack
+  * AWS_ACCESS_KEY_ID
+  * AWS_SECRET_ACCESS_KEY
+  * AWS_REGION
+  * IS_LOCAL = 'false'
+4.  `npm i`
+5.  `npm run migrate-data`
+
+#### Tables created
+
+* `Topcoder_X.CopilotPayment`
+* `Topcoder_X.Issue`
+* `Topcoder_X.OwnerUserGroup`
+* `Topcoder_X.OwnerUserTeam`
+* `Topcoder_X.Project`
+* `Topcoder_X.User`
+* `Topcoder_X.UserMapping`
+
+
+## Deploy latest code
+
+* Deploy the latest code from `master` to Heroku:
+  * topcoder-x-receiver
+  * topcoder-x-processor
+  * topcoder-x-ui
+
+Update the AWS Dynamo config values in Heroku:
+
+* AWS_ACCESS_KEY_ID
+* AWS_SECRET_ACCESS_KEY
+* IS_LOCAL='false'
+* AWS_DYNAMODB_REGION
+* AWS_REGION

DynamoDBMigration.md

@@ -47,7 +47,10 @@ npm run lint
 - post /projects/hook - create webhooks in the project repository
 - GET /users/settings - gets the current user's setup
 - GET /users/accessToken - gets the user's access token
-  
+
+- POST /issues - create an issue to Gitlab/Github
+- POST /issues/recreate - recreate an issue DB and its challenge
+
 - GET /health - gets the app health
 
 ## Configuration
@@ -65,11 +68,11 @@ Server should be started at port 80.
 ## Heroku Deployment
 Follow the below steps to deploy the app to heroku
 1. `heroku login`
-1. `heroku create`
-1. `heroku addons:create mongolab`
-1. `heroku config:set NPM_CONFIG_PRODUCTION=false` so that heroku will install dev dependencies
-1. `git push heroku master` or `git push heroku develop:master` to deploy develop branch
-1. `heroku open` to load the app on browser
+2. `heroku create`
+3. `heroku addons:create mongolab`
+4. `heroku config:set NPM_CONFIG_PRODUCTION=false` so that heroku will install dev dependencies
+5. `git push heroku master` or `git push heroku develop:master` to deploy develop branch
+6. `heroku open` to load the app on browser
 
 Note: heroku domain should match subdomain of topcoder-dev or topcoder depending upon target topcoder environment
 

README.md

@@ -1,6 +1,6 @@
 # Topcoder X overview
 
-Topcoder-X is a set of applications and services that allow a copilot or Topcoder customer to manage work directly through Gitlab or Github.  When an issue is created in a Gitlab or Github project set up in Topcoder-X, Topcoder-X will create a Topcoder challenge to mirror the Gitlab or Github issue, and it will ensure that the challenge has the correct prize, copilot, assignee, description, and title.  As the Gitlab or Github issue is updated, Topcoder-X will ensure that the Topcoder challenge associated with the issue is updated appropriately.  When the Gitlab or Github issue is closed, Topcoder-X will activate and close the Topcoder challenge, ensuring that the members get paid as expected.  
+Topcoder-X is a set of applications and services that allow a copilot or Topcoder customer to manage work directly through Gitlab or Github.  When an issue is created in a Gitlab or Github project set up in Topcoder-X, Topcoder-X will create a Topcoder challenge to mirror the Gitlab or Github issue, and it will ensure that the challenge has the correct prize, copilot, assignee, description, and title.  As the Gitlab or Github issue is updated, Topcoder-X will ensure that the Topcoder challenge associated with the issue is updated appropriately.  When the Gitlab or Github issue is closed, Topcoder-X will activate and close the Topcoder challenge, ensuring that the members get paid as expected.
 
 At each step of the process, Topcoder-X will add comments to the Gitlab or Github project, ensuring that the members know where the Topcoder challenge is and what the status of the challenge is.
 
@@ -10,7 +10,7 @@ The information is updated in real time based on webhook integrations with Gitla
 
 ## Dependencies
 * NodeJS 8+
-* MongoDB 3.2
+* DynamoDB
 * Kafka
 * nodemon (for local development)
 
@@ -25,18 +25,21 @@ Topcoder-X comprises 3 pieces:
 All 3 pieces will be configured to use the same MongoDB and Kafka installations.
 
 
-## MongoDB
+## DynamoDB
 
-The MongoDB can be created using default options.  Just make sure that it is configured properly as `MONGODB_URI` in all 3 pieces:
+The DynamoDB can be created using default options.  Just make sure that it is configured properly as `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_REGION`, `IS_LOCAL` in all 3 pieces:
 
 * Topcoder-X processor
 * Topcoder-X receiver
 * Topcoder-X UI
 
-Sample from our development environment:
-
-`MONGODB_URI: mongodb://heroku_k366sw2n:<password>@ds135552.mlab.com:35552/heroku_k366sw2n`
-
+Sample from our local development environment:
+```
+AWS_ACCESS_KEY_ID: 'FAKE_ACCESS_KEY_ID'
+AWS_SECRET_ACCESS_KEY: 'FAKE_SECRET_ACCESS_KEY'
+AWS_REGION: 'FAKE_REGION'
+IS_LOCAL: true
+```
 ## Kafka
 
 Installing Kafka can be done either locally or using a cloud service.  You'll need to note how the service is configured and will have to update the configuration appropriately for the receiver, processor, and site.
@@ -56,7 +59,7 @@ KAFKA_CLIENT_CERT: <cert string>
 
 KAFKA_CLIENT_CERT_KEY: <cert string>
 
-KAFKA_HOST: silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
+KAFKA_URL: silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
 
 TOPIC: topcoder-x
 ```
@@ -67,7 +70,7 @@ So it would be updated from this:
 
 ```
   KAFKA_OPTIONS: {
-    connectionString: process.env.KAFKA_HOST || 'localhost:9092',
+    connectionString: process.env.KAFKA_URL || 'localhost:9092',
     ssl: {
       cert: process.env.KAFKA_CLIENT_CERT || fs.readFileSync('./kafka_client.cer'), // eslint-disable-line no-sync
       key: process.env.KAFKA_CLIENT_CERT_KEY || fs.readFileSync('./kafka_client.key'), // eslint-disable-line no-sync
@@ -79,15 +82,34 @@ To this:
 
 ```
   KAFKA_OPTIONS: {
-    connectionString: process.env.KAFKA_HOST || 'localhost:9092'
+    connectionString: process.env.KAFKA_URL || 'localhost:9092'
   },
 ```
 
+## Machine-to-machine (M2M) Token generation
+The `topcoder-x-processor` uses the Topcoder m2m token to interact with others Topcoder service.
+It needs to be configured properly. Please make sure the following items is configured:
+
+- `AUTH0_URL` The Auth0 URL for generating Machine-to-machine token
+- `AUTH0_AUDIENCE` The audience of Auth0 to generate M2M Token
+- `AUTH0_CLIENT_ID` The Auth0 ClientID for generating Machine-to-machine token
+- `AUTH0_CLIENT_SECRET` The Auth0 Client Secret for generating Machine-to-machine token
+
+
+For local deployment, configuring M2M token generation can use this provided account:
+```
+export AUTH0_URL=https://topcoder-dev.auth0.com/oauth/token
+export AUTH0_AUDIENCE=https://m2m.topcoder-dev.com/
+export AUTH0_CLIENT_ID=LU2Nt7YPHQ3lxrFNKitJ82syB4wIMR7G
+export AUTH0_CLIENT_SECRET=O8S2YOb-0lI4NS3smR4d4uf0VM9BN0y1Ra4ABRktGUPOXc34mUO25uJrCpU-TBAT
+```
+
+
 ## Local DNS setup
 
 For login to work, your local Topcoder-X-UI deployment needs to have a `*.topcoder-dev.com` DNS name.  Our development environment uses `x.topcoder-dev.com`
 
-You can make this change in your local `/etc/hosts` file.  
+You can make this change in your local `/etc/hosts` file.
 
 ```
 127.0.0.1   x.topcoder-dev.com
@@ -100,7 +122,7 @@ You can login with one of these sample accounts:
 
 ## Local webhook setup
 
-The hardest part of the setup may be ensuring that Gitlab and Github can make callbacks to your local environment.  You will have to ensure that your Topcoder-X receiver is publicly accessible on the public internet.  
+The hardest part of the setup may be ensuring that Gitlab and Github can make callbacks to your local environment.  You will have to ensure that your Topcoder-X receiver is publicly accessible on the public internet.
 
 If your ISP dynamically configures your IP address, you can use a dyndns service:
 
@@ -118,7 +140,7 @@ http://<publicly accessible domain name>:<port>/webhooks/gitlab
 #### Github
 
 ```
-https://<publicly accessible domain name>:<port>/webhooks/github  
+https://<publicly accessible domain name>:<port>/webhooks/github
 ```
 
 ## Account setup
@@ -153,7 +175,7 @@ Contest https://www.topcoder-dev.com/challenges/30052039 has been updated - it h
 
 ## Sample development configs
 
-For reference, this is what the sample configs look like in our development environment, which should closely match your local deployment environment. 
+For reference, this is what the sample configs look like in our development environment, which should closely match your local deployment environment.
 
 You can use the Gitlab and Github keys and secrets below, but you are also welcome to create your own.
 
@@ -165,7 +187,7 @@ EMAIL_SENDER_ADDRESS:         [email protected]
 ISSUE_BID_EMAIL_RECEIVER:     [email protected]
 KAFKA_CLIENT_CERT: <cert>
 KAFKA_CLIENT_CERT_KEY: <key>
-KAFKA_HOST:                   silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
+KAFKA_URL:                   silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
 LOG_LEVEL:                    debug
 MAILGUN_API_KEY:              key-5ebe7a0fae37a9008721ec0bfe5bdd95
 MAILGUN_DOMAIN:               sandbox3fcf4920781449f2a5293f8ef18e4bb6.mailgun.org
@@ -174,12 +196,19 @@ MAILGUN_SMTP_LOGIN:           [email protected]
 MAILGUN_SMTP_PASSWORD:        c8aefb446e76febdbc31d57ef30b9c10
 MAILGUN_SMTP_PORT:            587
 MAILGUN_SMTP_SERVER:          smtp.mailgun.org
-MONGODB_URI:                  mongodb://heroku_k366sw2n:<password>@ds135552.mlab.com:35552/heroku_k366sw2n
 NODE_DEBUG:                   app
 NODE_ENV:                     development
 NODE_MODULES_CACHE:           false
 NODE_TLS_REJECT_UNAUTHORIZED: 0
 TOPIC:                        topcoder-x
+AWS_ACCESS_KEY_ID:  FAKE_ACCESS_KEY_ID
+AWS_SECRET_ACCESS_KEY: FAKE_SECRET_ACCESS_KEY
+AWS_REGION: FAKE_REGION
+IS_LOCAL: true
+AUTH0_URL:                    https://topcoder-dev.auth0.com/oauth/token
+AUTH0_AUDIENCE:               https://m2m.topcoder-dev.com/
+AUTH0_CLIENT_ID:              LU2Nt7YPHQ3lxrFNKitJ82syB4wIMR7G
+AUTH0_CLIENT_SECRET:          O8S2YOb-0lI4NS3smR4d4uf0VM9BN0y1Ra4ABRktGUPOXc34mUO25uJrCpU-TBAT
 ```
 
 #### Topcoder-X receiver
@@ -189,12 +218,15 @@ Justins-Mac-Pro:~ justingasper$ heroku config --app topcoder-x-receiver-dev
 === topcoder-x-receiver-dev Config Vars
 KAFKA_CLIENT_CERT: <cert>
 KAFKA_CLIENT_CERT_KEY: <key>
-KAFKA_HOST:                   silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
+KAFKA_URL:                   silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
 LOG_LEVEL:                    debug
-MONGODB_URI:                  mongodb://heroku_k366sw2n:<password>@ds135552.mlab.com:35552/heroku_k366sw2n
 NODE_ENV:                     development
 NODE_TLS_REJECT_UNAUTHORIZED: 0
 TOPIC:                        topcoder-x
+AWS_ACCESS_KEY_ID:  FAKE_ACCESS_KEY_ID
+AWS_SECRET_ACCESS_KEY: FAKE_SECRET_ACCESS_KEY
+AWS_REGION: FAKE_REGION
+IS_LOCAL: true
 ```
 
 #### Topcoder-X UI
@@ -210,12 +242,17 @@ GITLAB_CLIENT_SECRET:  70367d8255e160828ae47f35ff71723202afc7be1f29a4c7319bc82c4
 HOOK_BASE_URL:         https://topcoder-x-receiver-dev.herokuapp.com
 KAFKA_CLIENT_CERT:  <cert>
 KAFKA_CLIENT_CERT_KEY: <key>
-KAFKA_HOST:            silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
-MONGODB_URI:           mongodb://heroku_k366sw2n:<password>@ds135552.mlab.com:35552/heroku_k366sw2n
+KAFKA_URL:            silver-craft-01.srvs.cloudkafka.com:9093,silver-craft-01.srvs.cloudkafka.com:9094
 NPM_CONFIG_PRODUCTION: false
 SESSION_SECRET:        kjsdfkj34857
 TC_LOGIN_URL:          https://accounts.topcoder-dev.com/member
 TC_USER_PROFILE_URL:   http://api.topcoder-dev.com/v2/user/profile
 TOPIC:                 topcoder-x
 WEBSITE:               https://x.topcoder-dev.com
-```
+AWS_ACCESS_KEY_ID:  FAKE_ACCESS_KEY_ID
+AWS_SECRET_ACCESS_KEY: FAKE_SECRET_ACCESS_KEY
+AWS_REGION: FAKE_REGION
+IS_LOCAL: true
+TC_LOGIN_URL: https://accounts.topcoder-dev.com/member
+TC_USER_PROFILE_URL: https://api.topcoder-dev.com/v2/user/profile
+```

TopcoderXDeploy.md

@@ -0,0 +1,22 @@
+#!/bin/bash
+set -eo pipefail
+APP_NAME="topcoder-x-ui"
+UPDATE_CACHE=""
+docker-compose -f docker/docker-compose.yml build $APP_NAME
+docker create --name app $APP_NAME:latest
+
+if [ -d node_modules ]
+then
+  mv package-lock.json old-package-lock.json
+  docker cp app:/$APP_NAME/package-lock.json package-lock.json
+  set +eo pipefail
+  UPDATE_CACHE=$(cmp package-lock.json old-package-lock.json)
+  set -eo pipefail
+else
+  UPDATE_CACHE=1
+fi
+
+if [ "$UPDATE_CACHE" == 1 ]
+then
+  docker cp app:/$APP_NAME/node_modules .
+fi