Skip to content

Latest commit

 

History

2,773 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Emissions Data Management API

License Quality Gate Status Develop CI/CD Release CI/CD Issues Forks Stars Open in Visual Studio Code

Description

Manages emissions data for the EPA CAMD Business Systems. The emissions API endpoints return the hourly values for the measured parameters, calculated hourly emissions values, control technologies, unit type, and unit fuel types for the associated unit described in a facility’s monitoring plan.

Getting Started

Follow these instructions to get the project up and running correctly.

Installing

  1. Open a terminal and navigate to the directory where you wish to store the repository.
  2. Clone the repository using one of the following git cli commands or using your favorit Git management software
    Using SSH
    $ git clone git@github.com:US-EPA-CAMD/easey-emissions-api.git
    
    Using HTTPS
    $ git clone https://github.com/US-EPA-CAMD/easey-emissions-api.git
    
  3. Navigate to the projects root directory
    $ cd easey-emissions-api
    
  4. Install package dependencies
    $ yarn install
    

Configuration

The Emissions API uses a number of environment variables to properly configure the api. The following is the list of configureble values and their default setting.

Typescript Var Name Environment Var Name Default Value Comment
name N/A emissions-api Fixed value
host EASEY_EMISSIONS_API_HOST localhost Configurable
port EASEY_EMISSIONS_API_PORT 8040 Configurable
path EASEY_EMISSIONS_API_PATH emissions-mgmt Configurable
title EASEY_EMISSIONS_API_TITLE Emissions Management Configurable
description EASEY_EMISSIONS_API_DESCRIPTION Emissions management API endpoints for apportioned emissions data (e.g. hourly, daily, monthly, annual, and ozone season) Configurable
env EASEY_EMISSIONS_API_ENV local-dev Configurable
apiKey EASEY_EMISSIONS_API_KEY *** Dynamically set by CI/CD workflow
enableApiKey EASEY_EMISSIONS_API_ENABLE_API_KEY false Configurable
secretToken EASEY_EMISSIONS_API_SECRET_TOKEN *** Dynamically set by CI/CD workflow
enableSecretToken EASEY_EMISSIONS_API_ENABLE_SECRET_TOKEN false Configurable
enableCors EASEY_EMISSIONS_API_ENABLE_CORS true Configurable
enableAuthToken EASEY_EMISSIONS_API_ENABLE_AUTH_TOKEN false Configurable
enableGlobalValidationPipes EASEY_EMISSIONS_API_ENABLE_GLOBAL_VALIDATION_PIPE true Configurable
version EASEY_EMISSIONS_API_VERSION v0.0.0 Dynamically set by CI/CD workflow
published EASEY_EMISSIONS_API_PUBLISHED local Dynamically set by CI/CD workflow
submissionDays EASEY_EMISSIONS_API_SUBMISSION_DAYS 38 Configurable
enableDebug EASEY_EMISSIONS_API_ENABLE_DEBUG false Configurable
currentUser EASEY_EMISSIONS_API_CURRENT_USER {} Configurable
perPageLimit EASEY_EMISSIONS_API_PAGINATION_MAX_PER_PAGE 500 Configurable
apiHost EASEY_API_GATEWAY_HOST api.epa.gov/easey/dev Configurable
authApi.uri EASEY_AUTH_API https://api.epa.gov/easey/dev/auth-mgmt Configurable
contentApi.uri EASEY_CONTENT_API https://api.epa.gov/easey/dev/content-mgmt Configurable

Environment Variables File

Database credentials are injected into the cloud.gov environments as part of the CI/CD deployment process therefore they do not need to be configured. However, when running locally for local development the following environment variables are required to be configured using a local .env file in the root of the project. PLEASE DO NOT commit the .env file to source control.

  • EASEY_EMISSIONS_API_ENABLE_DEBUG=true|false
  • EASEY_EMISSIONS_API_ENABLE_API_KEY=true|false
    • IF ABOVE IS TRUE THEN SET
      • EASEY_EMISSIONS_API_KEY={ask project dev/tech lead}
  • EASEY_EMISSIONS_API_ENABLE_AUTH_TOKEN=true|false
    • IF ABOVE IS TRUE THEN
      • USE AUTH API TO SIGNIN & GET AUTH TOKEN TO USE AS A BEARER TOKEN
    • IF ABOVE IS FALSE THEN SET
      • EASEY_EMISSIONS_API_CURRENT_USER={see below}
      • FORMAT: { "userId": "testuser", "roles": [ { "orisCode": 3, "role": "P" } ] }
  • EASEY_EMISSIONS_API_ENABLE_SECRET_TOKEN=true|false
    • IF ABOVE IS TRUE THEN SET
      • EASEY_EMISSIONS_API_SECRET_TOKEN={ask project dev/tech lead}

Please refer to our Getting Started instructions on how to configure the following environment variables & connect to the database.

  • EASEY_DB_HOST
  • EASEY_DB_PORT
  • EASEY_DB_NAME
  • EASEY_DB_USER
  • EASEY_DB_PWD

Building, Testing, & Running the application

From within the projects root directory run the following commands using the yarn command line interface

Run in development mode

$ yarn start:dev

Install/update package dependencies & run in development mode

$ yarn up

Unit tests

$ yarn test

Build

$ yarn build

Run in production mode

$ yarn start

API Endpoints

Please refer to the Emissions Management API Swagger Documentation for descriptions of the endpoints.
Dev Environment | Test Environment | Performance Environment | Beta Environment | Staging Environment

License & Contributing

This project is licensed under the MIT License. We encourage you to read this project’s License, Contributing Guidelines, and Code of Conduct.

Disclaimer

The United States Environmental Protection Agency (EPA) GitHub project code is provided on an "as is" basis and the user assumes responsibility for its use. EPA has relinquished control of the information and no longer has responsibility to protect the integrity , confidentiality, or availability of the information. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by EPA. The EPA seal and logo shall not be used in any manner to imply endorsement of any commercial product or activity by EPA or the United States Government.

About

NestJS REST API for managing Emissions Data

Topics

Resources

Code of conduct

Contributing

Stars

2 stars

Watchers

9 watching

Forks

Releases

Used by

Contributors

Languages