eq-cir-proxy-service

A service used by eQ Runner to request CIs from CIR, forward the instruments to the CIR Converter Service to convert them to the latest version, and return the updated instrument back to eQ Runner

---

Table of Contents

• Getting Started
  • Pre-requisites
  • Installation
• Development
  • Run Tests with Coverage
  • Linting and Formatting
  • View the local application
• Contributing
• License

Getting Started

To run the project locally, follow these steps:

Pre-requisites

Ensure you have the following installed:

1. Python: Version specified in .python-version. We recommend using pyenv for managing Python versions.
2. Poetry: This is used to manage package dependencies and virtual environments.
3. Docker
4. Operation System: Ubuntu/MacOS

Installation

1. Clone the repository and install the required dependencies.

   git clone https://github.com/ONSdigital/eq-cir-proxy-service.git

2. Install dependencies

   Poetry is used to manage dependencies in this project. For more information, read the Poetry documentation.

   To install all dependencies, including development dependencies, run:

   make install-dev

   To install only production dependencies, run:

   make install

3. Set the environment variable LOG_LEVEL.

   It can be set to INFO, DEBUG, WARN, ERROR - if not set, it will be set to INFO by default.

   make set-env-var

4. Run the application

   make run

Development

Get started with development by running the following commands. Before proceeding, make sure you have the development dependencies installed using the make install-dev command.

A Makefile is provided to simplify common development tasks. To view all available commands, run:

make

Run Tests with Coverage

The unit tests are written using the pytest framework. To run the tests and check coverage, run:

make test

Linting and Formatting

Various tools are used to lint and format the code in this project. These include:

• Black
• MegaLinter
• Mypy
• Pylint
• Ruff

Python

The project uses Ruff, pylint and black for linting and formatting of the Python code.

The tools are configured using the pyproject.toml file.

To lint the Python code, run:

make lint

To auto-format the Python code, and correct fixable linting issues, run:

make format

MegaLinter (Lint/Format non-python files)

MegaLinter is utilised to lint the non-python files in the project. It offers a single interface to execute a suite of linters for multiple languages and formats, ensuring adherence to best practices and maintaining consistency across the repository without the need to install each linter individually.

MegaLinter examines various file types and tools, including GitHub Actions, Shell scripts, Dockerfile, etc. It is configured using the .mega-linter.yml file.

To run MegaLinter, ensure you have Docker installed on your system.

Note: The initial run may take some time to download the Docker image. However, subsequent executions will be considerably faster due to Docker caching.

To start the linter and automatically rectify fixable issues, run:

make megalint

Endpoint documentation

• Instrument endpoint

View the local application

• Navigate to http://localhost:5050/docs to view the FastAPI application.
• Navigate to http://localhost:5050/ to view the response JSON.

Contributing

See CONTRIBUTING.md for details.

License

See LICENSE for details.