move from GH pages to @guardian/actions-static-site

[twrichards]

Given recent stability issues with GitHub pages, it made sense to host using https://github.com/guardian/actions-static-site
for consistency with the rest of the estate and deployments via riff-raff. Oh an we get Google auth 😃

Note that it's already used for https://tools.gutools.co.uk/ (https://github.com/guardian/tools-index, specifically https://github.com/guardian/tools-index/pull/138)

Additional Tasks

• ensure action has access to secrets.GU_RIFF_RAFF_ROLE_ARN - https://github.com/guardian/riffraff-platform/pull/165
• have the domain added to the Google project
• remove old DNS entry and deploy this manually to PROD first time
• set-up Continuous Deployment in riff-raff
• turn-off GH Pages hosting in settings of this repo (and delete the gh-pages branch I guess)

[akash1810]

It's non-obvious that this repository will be deployed with the Riff-Raff project deploy::editions-card-builder. Worth adding something to the README?

[rhystmills]

I'm not sure how to test this, any advice?

[twrichards]

I'm not sure how to test this, any advice?

Can't really test. Deploying without removing existing DNS entry will fail as it attempts to create GuCname. Here it is in riff-raff though...

...I've had a look at the artifacts that will get deployed in https://riffraff.gutools.co.uk/deployment/request/deployFiles?projectName=deploy%3A%3Aeditions-card-builder&id=140 and all looks fine to me.

Just waiting on getting the domain added to the allow list in the Google project.

[twrichards]

I'm inclined to deploy to PROD manually first time, before merging the PR.

[andrew-nowak]

test by deploying to this or some other alternative name first, then switching later? to avoid bringing down the real thing which is still accessible by some ISPs. hopefully the site doesn't hardcode its domain anywhere

Suggested change

	domain: editions-card-builder.gutools.co.uk
	domain: editions-card-builder-2.gutools.co.uk

[twrichards]

test by deploying to this or some other alternative name first, then switching later? to avoid bringing down the real thing which is still accessible by some ISPs. hopefully the site doesn't hardcode its domain anywhere

I thought about this, but that leaves behind detritus in the deployTools account, plus DevX will need to add the domain to the google account and remove after. If somebody from @guardian/digital-cms would like to please review, and they also don't want to take the risk then I'm happy to do Andrew's suggestion and pair with DevX to cleanup after.

[twrichards]

Manually deployed to PROD via actions-static-site. Thank you to @jacobwinch for DNS changes and pairing on the release.

[prout-bot]

Overdue on PROD (merged by @twrichards 10 minutes and 4 seconds ago) What's gone wrong?