* Moving the web constants to the app config for more flexibility
* removing personal integrations from QA
* changing the PayPal Configuration setup to match the pattern in the services module
* removing the webConstants file after successful test
* renaming the braintree config key to something more understandable
* adding a file to the QA container to enable easy tracking the version of the currently deployed web client
* adding another visual representation of the QA version
I have a device that is blocking navigation (per chrome dev tools) on the success callback for reasons unknown. After comparing with the captcha connector (which works flawlessly), the only difference I can find is that captcha doesn't do anything else after `document.location.replace` for mobile. I'm not sure if this is the culprit but it can't hurt to try.
* Set environment URLs in webpack config.
* Provide non NULL dev server
* QA env uses the pq TLD
* Include icons in qa env
* Move base configs to develop.
local configurations should be done in the `./config/local.json` file.
* Fix config override loading to default to development
* Standardize url formatting
* Limit QA settings to those set in production
* Set self hosted in a config
* Specify cloud instead of production
Self hosted and cloud are both production environments.
The ENV setting is used to specify the env type while
NODE_ENV specifies whether development error handling and services.
* Update config instructions
* Remove invalid json
* Change env `production` references to `cloud`
* Fix formatting
* adding a "global variable" syntax for env vars
* switching diff branch to a testing branch instead of master
* adding base branch to the PR creation
* adding the diff branch to be the base branch to branch off of
* switching the diff branch back to master
* updating the last half of the workflow to use the new global var format
* fixing syntax error
* changing the way we check the number of build status tries
* adding in the Crowdin Api Token env var to the main step
* Breaking up the Crowdin update step into smaller manageable steps
* fixing env var for the download step
* fixing build id env for download
* Fixing PR branch env vars
* adding in a different way of pushing if branch already exists
* fixing the git bot user
* switching back to npm install because duo_web_sdk is in the package-lock.json as an ssh url
* trying the workaround found in https://github.com/npm/cli/issues/2610
* adding in the jslib to see if that fixes the original problem. Removing the workaround to isolate the solution
* adding in back the workaround
