app/service/service_callback_api_schema.py

from app.schema_validation.definitions import https_url, uuid

create_service_callback_api_schema = {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "description": "POST service callback/inbound api schema",
    "type": "object",
    "title": "Create service callback/inbound api",
    "properties": {
        "url": https_url,
        "bearer_token": {"type": "string", "minLength": 10},
        "updated_by_id": uuid,
    },
    "required": ["url", "bearer_token", "updated_by_id"],
}

update_service_callback_api_schema = {
    "$schema": "http://json-schema.org/draft-07/schema#",
    "description": "POST service callback/inbound api schema",
    "type": "object",
    "title": "Create service callback/inbound api",
    "properties": {
        "url": https_url,
        "bearer_token": {"type": "string", "minLength": 10},
        "updated_by_id": uuid,
    },
    "required": ["updated_by_id"],
}
Run auto-correct on app/ and tests/ 2021-03-10 13:55:06 +00:00			`from app.schema_validation.definitions import https_url, uuid`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00
move service_inbound_api endpoints to their own blueprint try and reduce the size of the service blueprint :) 2017-11-29 16:28:01 +00:00			`create_service_callback_api_schema = {`
Use Draft-07 and Draft7Validator everywhere We were using the Draft4Validator in one place, so this updates it to the Draft7Validator instead. The schemas were mostly using draft 4 of the JSON schema, though there were a couple of schemas that were already of version 7. This updates them all to version 7, which is the latest version fully supported by the jsonschema Python package. There are some breaking changes in the newer version of the schema, but I could not see anywhere would these affect us. Some of these schemas were not valid in version 4, but are now valid in version 7 because `"required": []` was not valid in earlier versions. 2022-04-08 17:05:59 +01:00			`"$schema": "http://json-schema.org/draft-07/schema#",`
move service_inbound_api endpoints to their own blueprint try and reduce the size of the service blueprint :) 2017-11-29 16:28:01 +00:00			`"description": "POST service callback/inbound api schema",`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`"type": "object",`
move service_inbound_api endpoints to their own blueprint try and reduce the size of the service blueprint :) 2017-11-29 16:28:01 +00:00			`"title": "Create service callback/inbound api",`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`"properties": {`
			`"url": https_url,`
			`"bearer_token": {"type": "string", "minLength": 10},`
reformat 2023-08-29 14:54:30 -07:00			`"updated_by_id": uuid,`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`},`
reformat 2023-08-29 14:54:30 -07:00			`"required": ["url", "bearer_token", "updated_by_id"],`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`}`

move service_inbound_api endpoints to their own blueprint try and reduce the size of the service blueprint :) 2017-11-29 16:28:01 +00:00			`update_service_callback_api_schema = {`
Use Draft-07 and Draft7Validator everywhere We were using the Draft4Validator in one place, so this updates it to the Draft7Validator instead. The schemas were mostly using draft 4 of the JSON schema, though there were a couple of schemas that were already of version 7. This updates them all to version 7, which is the latest version fully supported by the jsonschema Python package. There are some breaking changes in the newer version of the schema, but I could not see anywhere would these affect us. Some of these schemas were not valid in version 4, but are now valid in version 7 because `"required": []` was not valid in earlier versions. 2022-04-08 17:05:59 +01:00			`"$schema": "http://json-schema.org/draft-07/schema#",`
move service_inbound_api endpoints to their own blueprint try and reduce the size of the service blueprint :) 2017-11-29 16:28:01 +00:00			`"description": "POST service callback/inbound api schema",`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`"type": "object",`
move service_inbound_api endpoints to their own blueprint try and reduce the size of the service blueprint :) 2017-11-29 16:28:01 +00:00			`"title": "Create service callback/inbound api",`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`"properties": {`
			`"url": https_url,`
			`"bearer_token": {"type": "string", "minLength": 10},`
reformat 2023-08-29 14:54:30 -07:00			`"updated_by_id": uuid,`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`},`
reformat 2023-08-29 14:54:30 -07:00			`"required": ["updated_by_id"],`
New table to store the inbound api information for a service. The table is versioned. There is a new endpoint to create the inbound api and one to update it. 2017-06-15 11:32:51 +01:00			`}`