default.yaml

port: 5000
asyncRequestApi: {
    url: https://publish-api.planning.data.gov.uk,
    port: 8082,
    requestsEndpoint: 'requests',
    requestTimeout: 50000
}
maintenance: {
    serviceUnavailable: false,
    upTime: "9am on Monday 19 November 2024"
}
aws: {
    region: eu-west-2,
    bucket: '',
    s3ForcePathStyle: false,
}
# ToDo: url and name might need updating
url: 'https://submit.planning.data.gov.uk'
mainWebsiteUrl: https://www.planning.data.gov.uk
# NOTE: this property is deprecated, use serviceNames instead
serviceName: 'Submit and update your planning data'
# NOTE: the keys in this map are sometimes referred to as "serviceType" in the templates
serviceNames: {
    submit: 'Submit your planning data',
    check: 'Check your planning data',
    manage: 'Submit and update your planning data'
}
datasetteUrl: 'https://datasette.planning.data.gov.uk'
checkService:
    # used as User-Agent header when checking the accessibility
    # of user supplied URLs
    userAgent: 'GOVUK Planning Data: Check Service'
templateContent:
    feedbackLink: 'https://docs.google.com/forms/d/e/1FAIpQLSdYXqY0Aaket9XJBiGDhSL_CD_cxHZxgvQCFZZtdURdvvIY5A/viewform'
    homepageUrl: '/'
email: {
    templates: {
        RequestTemplateId: 'fa1c2b51-3c91-4f9d-9a18-83639164d552',
        AcknowledgementTemplateId: '2a4dff6d-78c4-4fea-a489-c97485453807'
    },
    dataManagementEmail: 'fakeemail@fakemail.com'
}
validations: {
    maxFileSize: 100000000
}
contact:
  issues:
    # description: should be used for general issues, e.g. if user lands on 404 doesn't know how to proceed
    email: digitalland@communities.gov.uk
datasetsConfig:
  article-4-direction:
    guidanceUrl: /guidance/specifications/article-4-direction
    entityDisplayName:
      base: article 4 direction
      variable: area
  article-4-direction-area:
    guidanceUrl: /guidance/specifications/article-4-direction
    entityDisplayName:
      base: article 4 direction
      variable: area
  brownfield-land:
    guidanceUrl: https://www.gov.uk/government/publications/brownfield-land-registers-data-standard/publish-your-brownfield-land-data
    entityDisplayName:
      base: brownfield
      variable: land
  conservation-area:
    guidanceUrl: /guidance/specifications/conservation-area
    entityDisplayName:
      base: conservation
      variable: area
  conservation-area-document:
    guidanceUrl: /guidance/specifications/conservation-area
    entityDisplayName:
      base: conservation
      variable: area
  tree-preservation-order:
    guidanceUrl: /guidance/specifications/tree-preservation-order
    entityDisplayName:
      base: tree preservation
      variable: order
  tree-preservation-zone:
    guidanceUrl: /guidance/specifications/tree-preservation-order
    entityDisplayName:
      base: tree preservation
      variable: zone
  tree:
    guidanceUrl: /guidance/specifications/tree-preservation-order
    entityDisplayName:
      variable: tree
  listed-building:
    guidanceUrl: /guidance/specifications/listed-building
    entityDisplayName:
      base: listed
      variable: building
  listed-building-outline:
    guidanceUrl: /guidance/specifications/listed-building
    entityDisplayName:
      base: listed building
      variable: outline
tablePageLength: 50
jira: {
  requestTypeId: 1
}
features:
  issueSpecificationGuidance:
    enabled: true
  submitEndpointForm:
    enabled: false
  checkIssueDetailsPage:
    # https://github.com/digital-land/submit/issues/786
    # enabling this feature will cause the results page to present
    # links to individual issue pages
    enabled: true
  expectationOutOfBoundsTask:
    # this feature includes violated 'out of bounds' expectations
    # as 'tasks' on LPA overview pages etc.
    # https://github.com/digital-land/submit/issues/921
    enabled: true