feat(technicalkey): unexpected response for post policy-content - Purpose

[AnuragNagpure]

Description

Error message with http status code 400 that value is not allowed. Only backend stored purposes are allowed; any other should run on an error

Why

The implementation should include the following requirements:

When the tester provides an input value that is not supported for the specified purposes, the endpoint should generate an error.
The error message displayed to the user should ideally include a comprehensive list of all allowed values for the input.
Please ensure that the implementation adheres to these guidelines.

Issue

#68

Checklist

Please delete options that are not relevant.

• I have followed the contributing guidelines
• I have performed a self-review of my own code
• I have successfully tested my changes locally
• I have added tests that prove my changes work
• I have checked that new and existing tests pass locally with my changes
• I have commented my code, particularly in hard-to-understand areas
• I have added copyright and license headers, footers (for .md files) or files (for images)

[Phil91]

With the current implementation only the left operand gets checked, the ticket mentions to check the value. at the moment there is no configuration for purposes to a given value set. I think we need to clarify with @jjeroch

[AnuragNagpure]

Below changes are added as per description.

PolicyAttributes

remove - ID Trace 3.1 from policy_attributes

map attribute_values:

purpose.trace.v1.traceBattery
purpose.trace.v1.aspects
purpose.trace.v1.qualityanalysis

to polcy_id = 01a0fba3-9b6e-435a-b045-e0e890c300c2

Policies

remove the following policies including the linked data

01a0fba3-9b6e-435a-b045-e0e890c300b7
01a0fba3-9b6e-435a-b045-e0e890c300b8
01a0fba3-9b6e-435a-b045-e0e890c300b9

add a check to the post endpoint to validate the value of the request to be existing in the attributes_value table for the given policy

/cc @jjeroch