Skip to content

HP-2319 | Check allowed data fields when querying profiles #772

HP-2319 | Check allowed data fields when querying profiles

HP-2319 | Check allowed data fields when querying profiles #772

Triggered via pull request May 7, 2024 11:12
Status Failure
Total duration 4m 22s
Artifacts

ci.yml

on: pull_request
Tests
4m 14s
Tests
Commitlint
12s
Commitlint
Coding style - black
8s
Coding style - black
Coding style - flake8
6s
Coding style - flake8
Coding style - isort
7s
Coding style - isort
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Commitlint
You have commit messages with errors ⧗ input: feat: add middleware for checking allowed data fields In profile and myProfile query there should be checked the service for allowed fields. This adds middleware and mixin class for nodes for checking the queried field exists in service's allowed data fields Refs HP-2319 ✖ body's lines must not be longer than 72 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint ⧗ input: feat: add feature flag for checking allowed data fields Adds setting for allowed data field check named as: ENABLE_ALLOWED_DATA_FIELDS_RESTRICTION The setting defaults False. When False, app sends warning message to sentry, when there is query trying to access a field which is not in service's allowed_data_fields Refs HP-2319 ✖ body's lines must not be longer than 72 characters [body-max-line-length] ✖ found 1 problems, 0 warnings ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
Tests
Process completed with exit code 1.