chore: upgrade to Play v3

tjsilver commented 10 months ago

What does this change?

Upgrades Play to v3.0.1.
Upgrades various other dependencies to enable this to work.
Bumps the version of Security HQ to 0.5.0.
One change to Scala config has been made to remove an import for GoogleServiceAccount that doesn't exist in the later version of Google Auth.

What is the value of this?

This has been done to remove our dependence on Akka. Play v3 uses Pekko instead.

Will this require CloudFormation and/or updates to the AWS StackSet?

I don't think so.

Will this require changes to config?

I have updated the local DEV config in S3 with a longer application secret, as required by Play v3. I don't think PROD will be affected.

github-actions[bot] commented 10 months ago

Deploy build 2735 of `security-hq` to CODE

All deployment options

- [Deploy build 2735 of `security-hq` to CODE](https://riffraff.gutools.co.uk/deployment/deployAgain?project=security-hq&build=2735&stage=CODE&updateStrategy=MostlyHarmless&action=deploy) - [Deploy parts of build 2735 to CODE by previewing it first](https://riffraff.gutools.co.uk/preview/yaml?project=security-hq&build=2735&stage=CODE&updateStrategy=MostlyHarmless) - [What's on CODE right now?](https://riffraff.gutools.co.uk/deployment/history?projectName=security-hq&stage=CODE)

From guardian/actions-riff-raff.

adamnfish commented 10 months ago

With the caveat that we need to check if the tests are running!

guardian / security-hq