govuk_env_sync::tasks:
  push_licensify: &push_licensify
    ensure: present
    hour: '4'
    minute: '0'
    action: push
    dbms: mongo
    storagebackend: s3
    database: licensify
    temppath: /var/lib/mongodb/.dumps
    url: govuk-integration-database-backups
    path: mongo-licensing

  push_licensify_audit:
    <<: *push_licensify
    database: licensify-audit

  push_licensify_refdata:
    <<: *push_licensify
    database: licensify-refdata

  pull_licensify: &pull_licensify
    ensure: present
    hour: '5'
    minute: '0'
    action: pull
    dbms: mongo
    storagebackend: s3
    database: licensify
    temppath: /var/lib/mongodb/.dumps
    url: govuk-staging-database-backups
    path: mongo-licensing

  pull_licensify_audit:
    <<: *pull_licensify
    database: licensify-audit

  pull_licensify_refdata:
    <<: *pull_licensify
    database: licensify-refdata

govuk_env_sync::tasks:
  push_licensify: &push_licensify
    ensure: present
    hour: '4'
    minute: '0'
    action: push
    dbms: mongo
    storagebackend: s3
    database: licensify
    temppath: /var/lib/mongodb/.dumps
    url: govuk-integration-database-backups
    path: mongo-licensing

  push_licensify_audit:
    <<: *push_licensify
    database: licensify-audit

  push_licensify_refdata:
    <<: *push_licensify
    database: licensify-refdata

Revert "Pull licensing staging databases into integration"
Revert "Pull licensing staging databases into integration"

This reverts commit 6a0576f7b040556279f316e8fbcbb220fce8c7de.

I've noticed that the data from staging will contain some payment
records and various other potentially sensitive information. Until we
know for sure we want this in integration, I thought it was best to not
pull from staging into integration.
