Minimal API for the Land Use Planning Public and Admin apps -->
Before running the api, you must set some environment variables:
- MINIO_HOST='foo.pathfinder.gov.bc.ca'
- MINIO_ACCESS_KEY='xxxx'
- MINIO_SECRET_KEY='xxxx'
- KEYCLOAK_ENABLED=true
- MONGODB_DATABASE='landuseplanning'
One way to do this is to edit your ~/.bash_profile file to contain:
export MONGODB_DATABASE="landuseplanning"
export MINIO_HOST="foo.pathfinder.gov.bc.ca"
export MINIO_ACCESS_KEY="xxxx"
export MINIO_SECRET_KEY="xxxx"
export KEYCLOAK_ENABLED=true
Please note that these values are case sensitive so don't use upper-case TRUE for example.
Don't forget to reload your .bash_profile file so that your terminal environment is up to date with the correct values
source ~/.bash_profile
env
The above env command will show you your environment variables and allow you to check that the correct values are present.
Start the server by running npm run start-watch
| Technology | Version | Website | Description |
|---|---|---|---|
| node | 12.x.x | https://nodejs.org/en/ | JavaScript Runtime |
| npm | 6.x.x | https://www.npmjs.com/ | Node Package Manager |
| yarn | latest | https://yarnpkg.com/en/ | Package Manager (more efficient than npm) |
| mongodb | 3.6 | https://docs.mongodb.com/v3.6/installation/ | NoSQL database |
Install Node + NPM
Note: Windows users can use NVM Windows to install and manage multiple versions of Node+Npm.
Install Yarn
npm install -g yarn
Install MongoDB
-
Download dependencies:
yarn install -
Run the app:
npm start -
Go to http://localhost:3000/api/docs to verify that the application is running.
Note: To change the default port edit
swagger.yaml. -
POST
http://localhost:3000/api/login/tokenwith the following body:
{
"username": #{username},
"password": #{password}
}
The API is defined in swagger.yaml.
If the this landuseplanning-api is running locally, you can view the api docs at: http://localhost:3000/api/docs/
This project uses npm package swagger-tools via ./app.js to automatically generate the express server and its routes.
Recommend reviewing the Open API Specification before making any changes to the swagger.yaml file.
We use a version manager so as to allow concurrent versions of node and other software. asdf is recommended. Installation of asdf and required node packages is covered here
If possible, acquire a dump of the database from one of the live environments.
To make sure you don't have an existing old copy (careful, this is destructive):
mongo
use epic
db.dropDatabase()
- Download and unzip archived dump file.
- Restore the dump into your local mongo:
mongo
use landuseplanning
db.dropDatabase()
Described in seed README
To restore the database dump you have from the old epic system (ie ESM):
mongorestore -d epic dump/[old_database_name_most_likely_esm]
Then run the contents of dataload against that database. You may need to edit the commands slightly to match your db name or to remove the ".gz --gzip" portion if your dump unpacks as straight ".bson" files.
This app is designed to be run on Node 12.22.12 in Openshift. As a result, almost all modern ECMAScript features are available except for:
- The nullish coalescing operator
- Optional object chaining
See here for more details on ES feature availability: https://node.green/
An overview of the EPIC test stack can be found here.
This project is using jest as a testing framework. You can run tests with
yarn test or jest. Running either command with the --watch flag will re-run the tests every time a file is changed.
To run the tests in one file, simply pass the path of the file name e.g. jest api/test/search.test.js --watch. To run only one test in that file, chain the .only command e.g. test.only("Search returns results", () => {}).
The MOST IMPORTANT thing to know about this project's test environment is the router setup. At the time of writing this, it wasn't possible to get swagger-tools router working in the test environment. As a result, all tests COMPLETELY bypass the real life swagger-tools router. Instead, a middleware router called supertest is used to map routes to controller actions. In each controller test, you will need to add code like the following:
const test_helper = require('./test_helper');
const app = test_helper.app;
const featureController = require('../controllers/feature.js');
const fieldNames = ['tags', 'properties', 'applicationID'];
app.get('/api/feature/:id', function(req, res) {
let params = test_helper.buildParams({'featureId': req.params.id});
let paramsWithFeatureId = test_helper.createPublicSwaggerParams(fieldNames, params);
return featureController.protectedGet(paramsWithFeatureId, res);
});
test("GET /api/feature/:id returns 200", done => {
request(app)
.get('/api/feature/AAABBB')
.expect(200)
.then(done)
});This code will stand in for the swagger-tools router, and help build the objects that swagger-tools magically generates when HTTP calls go through it's router. The above code will send an object like below to the api/controllers/feature.js controller protectedGet function as the first parameter (typically called args).
{
swagger: {
params: {
auth_payload: {
scopes: ['sysadmin', 'public'],
userID: null
},
fields: {
value: ['tags', 'properties', 'applicationID']
},
featureId: {
value: 'AAABBB'
}
}
}
}Unfortunately, this results in a lot of boilerplate code in each of the controller tests. There are some helpers to reduce the amount you need to write, but you will still need to check the parameter field names sent by your middleware router match what the controller(and swagger router) expect. However, this method results in pretty effective integration tests as they exercise the controller code and save objects in the database.
The tests run on an in-memory MongoDB server, using the mongodb-memory-server package. The setup can be viewed at test_helper.js, and additional config in [config/mongoose_options.js]. It is currently configured to wipe out the database after each test run to prevent database pollution.
Factory-Girl is used to easily create models(persisted to db) for testing purposes.
External http calls (such as GETs to BCGW) are mocked with a tool called nock. Currently sample JSON responses are stored in the test/fixtures directory. This allows you to intercept a call to an external service such as bcgw, and respond with your own sample data.
const bcgwDomain = 'https://openmaps.gov.bc.ca';
const searchPath = '/geo/pub/FOOO';
const crownlandsResponse = require('./fixtures/crownlands_response.json');
var bcgw = nock(bcgwDomain);
let dispositionId = 666666;
beforeEach(() => {
bcgw.get(searchPath + urlEncodedDispositionId)
.reply(200, crownlandsResponse);
});
test('returns the features data from bcgw', done => {
request(app).get('/api/public/search/bcgw/dispositionTransactionId/' + dispositionId)
.expect(200)
.then(response => {
let firstFeature = response.body.features[0];
expect(firstFeature).toHaveProperty('properties');
expect(firstFeature.properties).toHaveProperty('DISPOSITION_TRANSACTION_SID');
done();
});
});Recall the environment variables we need for local dev:
- MINIO_HOST='foo.pathfinder.gov.bc.ca'
- MINIO_ACCESS_KEY='xxxx'
- MINIO_SECRET_KEY='xxxx'
- KEYCLOAK_ENABLED=true
- MONGODB_DATABASE='epic'
- SILENCE_DEFAULT_LOG=false
To get actual values for the above fields in the deployed environments, examine the openshift environment you wish to target:
oc project [projectname]
oc get routes | grep 'minio'
oc get secrets | grep 'minio'
Note: SILENCE_DEFAULT_LOG is used for local development only. See Logging below.
You will not be able to see the above value of the secret if you try examine it. You will only see the encrypted values. Approach your team member with admin access in the openshift project in order to get the access key and secret key values for the secret name you got from the above command. Make sure to ask for the correct environment (dev, test, prod) for the appropriate values.
The winston package is used to log nearly every operation in the app. console.log is discouraged in favour of winston.
When developing, one may choose to silence the verbose log output to be able to focus on specific operations. To do this:
- Set the SILENCE_DEFAULT_LOG environment variable to "true".
- Switch the
winston.loggers.get()call argument fromdefaultLogtodevLog. - When you're finished, restore all logging to use
defaultLog.
The Winston loggers have been set up in config/loggers.js.
API Controllers begin with a log output that states:
- The model name
- The level of access
- The HTTP method
So an example log for a controller would be "COMMENT PERIOD PROTECTED GET."
![repo-mountie[bot] avatar](https://avatars.githubusercontent.com/in/19327?v=4 "repo-mountie[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent