Skip to main content

The HEA settings service.

Project description

HEA Server Settings Microservice

Research Informatics Shared Resource, Huntsman Cancer Institute, Salt Lake City, UT

The HEA Server Settings Microservice manages user and system settings.

Version 1.4.0

  • Bumped heaserver version to 1.48.0.
  • Added support for encrypted Mongo passwords.
  • New startup.py module to initialize logging before importing any third-party libraries.
  • New optional -e/--env command-line argument for setting the runtime environment (development, staging, or production). Logging is now configured based on this setting, unless the older -l/--logging argument is provided. The default value is development.
  • Logs are now scrubbed.
  • Added log files to .gitignore.

Version 1.3.1

  • Bumped heaserver version to 1.32.1.
  • The super_admin_default_permissions attribute is now an empty list.

Version 1.3.0

  • Bumped heaserver version to 1.30.1.
  • Removed CREATOR from permissions dropdowns in the properties metadata.
  • Added missing type attribute metadata to shares in the properties metadata.

Version 1.2.1

  • Bumped heaserver version to 1.28.1.

Version 1.2.0

  • Added support for python 3.12.
  • Added group permissions support.

Version 1.1.0

  • Make settings show based on permissions.
  • Make Credentials settings object expect CredentialsView actual objects.
  • Remove integration tests because they are duplicative.

Version 1

  • Initial release.

Runtime requirements

  • Python 3.10, 3.11, or 3.12.

Development environment

Build requirements

  • Any development environment is fine.
  • On Windows, you also will need:
  • On Mac, Xcode or the command line developer tools is required, found in the Apple Store app.
  • Python 3.10-3.12: Download and install Python from https://www.python.org, and select the options to install for all users and add Python to your environment variables. The install for all users option will help keep you from accidentally installing packages into your Python installation's site-packages directory instead of to your virtualenv environment, described below.
  • Create a virtualenv environment using the python -m venv <venv_directory> command, substituting <venv_directory> with the directory name of your virtual environment. Run source <venv_directory>/bin/activate (or <venv_directory>/Scripts/activate on Windows) to activate the virtual environment. You will need to activate the virtualenv every time before starting work, or your IDE may be able to do this for you automatically. Note that PyCharm will do this for you, but you have to create a new Terminal panel after you newly configure a project with your virtualenv.
  • From the project's root directory, and using the activated virtualenv, run pip install wheel followed by pip install -r requirements_dev.txt. Do NOT run python setup.py develop. It will break your environment.

Running tests

Run tests with the pytest command from the project root directory. To improve performance, run tests in multiple processes with pytest -n auto.

Running integration tests

Trying out the APIs

This microservice has Swagger3/OpenAPI support so that you can quickly test the APIs in a web browser. Do the following:

  • Install Docker, if it is not installed already.
  • Run the run-swaggerui.py file in your terminal. This file contains some test objects that are loaded into a MongoDB Docker container.
  • Go to http://127.0.0.1:8080/docs in your web browser.

Once run-swaggerui.py is running, you can also access the APIs via curl or other tool. For example, in Windows PowerShell, execute:

Invoke-RestMethod -Uri http://localhost:8080/components/ -Method GET -Headers @{'accept' = 'application/json'}`

In MacOS or Linux, the equivalent command is:

curl -X GET http://localhost:8080/components/ -H 'accept: application/json'

Packaging and releasing this project

See the RELEASING.md file for details.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

heaserver_settings-1.4.0.tar.gz (22.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

heaserver_settings-1.4.0-py3-none-any.whl (13.0 kB view details)

Uploaded Python 3

File details

Details for the file heaserver_settings-1.4.0.tar.gz.

File metadata

  • Download URL: heaserver_settings-1.4.0.tar.gz
  • Upload date:
  • Size: 22.1 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.12.7

File hashes

Hashes for heaserver_settings-1.4.0.tar.gz
Algorithm Hash digest
SHA256 eff2ed14aa6563541f32e1ae46b76b18d8c11d6d54ad431cfaaadac0db86eda8
MD5 13cf519d4df0f60dd8de0e6a3d48cf97
BLAKE2b-256 15d38e68606bb19a89dd9c4a05180804d75351421e39f0afb8a696b5c0927ce6

See more details on using hashes here.

File details

Details for the file heaserver_settings-1.4.0-py3-none-any.whl.

File metadata

File hashes

Hashes for heaserver_settings-1.4.0-py3-none-any.whl
Algorithm Hash digest
SHA256 75fa3305a286d3e306084df543f3698c8b9b8ff9270155bd0e3ece3c8bbe325d
MD5 5b0a834063560dac3fa204b6631a0786
BLAKE2b-256 26db33ad20b31d7918a4f90e1589e864365d60732a508f97a8758fd3467f1356

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page