Update sandbox DSI configuration

[Nitemaeric]

Context

We want to configure the Sandbox environment to work as it would in production. APIs will all read in real-life data from production APIs.

The difference for Sandbox is that it should not submit real information to external partners, such as the ESFA.

Changes proposed in this pull request

• Update DSI configuration in terraform/application/config/sandbox_app_env.yml to point to production DSI.
• Add "sandbox" domains to Production DSI configuration.
• Sandbox DSI secret has been added to the key vault.

Guidance to review

Considerations

• External APIs should be read-only.
• Writing to external partners, such as ESFA, should be configured to not go to actual external partners.

[github-actions]

Deployments

App	URL
Track & Pay	https://track-and-pay-1064.test.teacherservices.cloud
School Placements	https://manage-school-placements-1064.test.teacherservices.cloud

[ollietreend]

Writing to external partners, such as ESFA, should be configured to not go to actual external partners.

Is this already the case? Or does that need adding to this PR?

I'm also wondering about integrations like GOV.UK Notify. Will that send real-world emails to users, or are they caught?

[Nitemaeric]

Writing to external partners, such as ESFA, should be configured to not go to actual external partners.

Is this already the case? Or does that need adding to this PR?

I'm also wondering about integrations like GOV.UK Notify. Will that send real-world emails to users, or are they caught?

Sorry, didn't realise you responded to this.

It's the case for ESFA, where we don't want actual payments to go through. I'd assume things like, updating mentor TRNs and others, we wouldn't want to really be updated either.

That being said, I think emails are still important to actually be sent. This is because, we want the ability to invite users onto the sandbox platform.