app/letters/rest.py

from flask import Blueprint, jsonify, request

from app.celery.tasks import process_returned_letters_list
from app.config import QueueNames
from app.letters.letter_schemas import letter_references
from app.schema_validation import validate
from app.v2.errors import register_errors

letter_job = Blueprint("letter-job", __name__)
register_errors(letter_job)


@letter_job.route('/letters/returned', methods=['POST'])
def create_process_returned_letters_job():
    references = validate(request.get_json(), letter_references)

    process_returned_letters_list.apply_async([references['references']], queue=QueueNames.DATABASE)

    return jsonify(references=references['references']), 200
Run auto-correct on app/ and tests/ 2021-03-10 13:55:06 +00:00			`from flask import Blueprint, jsonify, request`
New endpoint to send a list of job ids to a queue. The task will be picked up by the FTP app. Given the list of job ids the tasks will get all the files from s3, aggregate them then send to dvla 2017-04-06 12:14:17 +01:00
Add a task to process returned letter lists Adds an API endpoint `/letters/returned` that accepts a list of notification references and creates a task to update their status. Adds a new task that uses the list of references to update the status of notifications to 'returned-letter'. The update is currently done using a single query and logs the number of changed records (including notification history records). This could potentially be done within the `/letters/returned` endpoint, but creating a job right away allows us to extend this more easily in the future (e.g. logging missing notifications or adding callbacks). The job is using the database tasks queue. 2018-08-31 16:49:06 +01:00			`from app.celery.tasks import process_returned_letters_list`
Remove letter-jobs api When we first built letters you could only send them via a CSV upload, initially we needed a way to send those files to dvla per job. We since stopped using this page. So let's delete it! 2018-11-15 17:24:37 +00:00			`from app.config import QueueNames`
			`from app.letters.letter_schemas import letter_references`
New endpoint to send a list of job ids to a queue. The task will be picked up by the FTP app. Given the list of job ids the tasks will get all the files from s3, aggregate them then send to dvla 2017-04-06 12:14:17 +01:00			`from app.schema_validation import validate`
Remove letter-jobs api When we first built letters you could only send them via a CSV upload, initially we needed a way to send those files to dvla per job. We since stopped using this page. So let's delete it! 2018-11-15 17:24:37 +00:00			`from app.v2.errors import register_errors`
New endpoint to send a list of job ids to a queue. The task will be picked up by the FTP app. Given the list of job ids the tasks will get all the files from s3, aggregate them then send to dvla 2017-04-06 12:14:17 +01:00
			`letter_job = Blueprint("letter-job", __name__)`
			`register_errors(letter_job)`


Add a task to process returned letter lists Adds an API endpoint `/letters/returned` that accepts a list of notification references and creates a task to update their status. Adds a new task that uses the list of references to update the status of notifications to 'returned-letter'. The update is currently done using a single query and logs the number of changed records (including notification history records). This could potentially be done within the `/letters/returned` endpoint, but creating a job right away allows us to extend this more easily in the future (e.g. logging missing notifications or adding callbacks). The job is using the database tasks queue. 2018-08-31 16:49:06 +01:00			`@letter_job.route('/letters/returned', methods=['POST'])`
			`def create_process_returned_letters_job():`
			`references = validate(request.get_json(), letter_references)`

			`process_returned_letters_list.apply_async([references['references']], queue=QueueNames.DATABASE)`

			`return jsonify(references=references['references']), 200`