From efeacf5700b81c35f6756887e6d385180b797f3d Mon Sep 17 00:00:00 2001 From: Rachael Booth Date: Fri, 7 Jul 2023 09:19:32 +0100 Subject: [PATCH] Fix out of date docs about xml export trigger (#1760) --- docs/exports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/exports.md b/docs/exports.md index 7a31ece3c..f16efe893 100644 --- a/docs/exports.md +++ b/docs/exports.md @@ -10,7 +10,7 @@ This is done via XML exports saved in an S3 bucket located in the DAP VPC using Initially the application database field names and field types were chosen to match the existing CDS data as closely as possible to minimise the amount of transformation needed. This has led to a less than optimal data model though and increasingly we should look to transform at the mapping layer where beneficial for our application. -The export service is triggered nightly using [Gov PaaS tasks](https://docs.cloudfoundry.org/devguide/using-tasks.html). These tasks are triggered from a GitHub action, as Gov PaaS does not currently support the Cloud Foundry Task Scheduler. +We have a cron job triggering the export service daily at 5am. The S3 bucket is located in the DAP VPC rather than the application VPC as DAP runs in an AWS account directly so access to the S3 bucket can be restricted to only the IPs used by the application. This is not possible the other way around as [Gov PaaS does not support restricting S3 access by IP](https://github.com/alphagov/paas-roadmap/issues/107).