Setup Cloudflare deploys via Github Action

[buberdds]

Requires: CLOUDFRONT_API_TOKEN and CLOUDFRONT_ACCOUNT_ID secrets on repo level
https://github.com/oasisprotocol/explorer/settings/secrets/actions

Setup:

• API Token (https://github.com/cloudflare/pages-action#generate-an-api-token)
  https://dash.cloudflare.com/profile/api-tokens -> Create ->
  At the bottom under Custom Token -> Get started ->
  Provide Token name ->
  Under Permissions, select Account, Cloudflare Pages and Edit
  Select Continue to summary > Create Token.

• Account ID
  Dashboard home -> Left side navigation -> Workers -> Overview -> Account ID is listed on the right side

• Suspend Github CloudFlare github app https://github.com/oasisprotocol/explorer/settings/installations

---

• CloudFlare builds&deploys are slow (> 3m)
• Currently we control everything via CloudFlare dashboard options and most of us cannot access it
• GH action would allow us to omit CloudFlare Pages limit (1 deploy per repo) if we would like to deploy Storybook one day

---

Sample output:
default: buberdds#20
skipped for Renovate bot: buberdds#22

[cloudflare-pages]

Deploying with    Cloudflare Pages

Latest commit:	cfe1f45
Status:	✅  Deploy successful!
Preview URL:	https://27574a63.oasis-explorer.pages.dev
Branch Preview URL:	https://mz-cloudflare.oasis-explorer.pages.dev

View logs

[github-actions]

Deployed to Cloudflare Pages

Latest commit:
Status:	✅ Deploy successful!
Preview URL:

[lukaw3d]

Looks like it would work well 👍 needs a token

[buberdds]

@tjanez API Token description updated. We only need Cloudflare Pages Edit permission. Tested on fork buberdds#30

https://github.com/cloudflare/pages-action#generate-an-api-token

https://dash.cloudflare.com/profile/api-tokens -> Create ->
At the bottom under Custom Token -> Get started ->
Provide Token name ->
Under Permissions, select Account, Cloudflare Pages and Edit
Select Continue to summary > Create Token

[tjanez]

I've added the secrets, so let's check if this works.

[buberdds]

Thanks, secrets look Ok. We can remove Github App integration before merge. https://github.com/oasisprotocol/explorer/settings/installations

[lukaw3d]

Something is wrong:

Old bot: Latest commit: 62f8165, Preview URL: https://ee885e51.oasis-explorer.pages.dev/
open, see footer "Version: 62f8165"

New workflow: Latest commit: 62f8165d829668803f55e405d4d33ddc2af61b37, Preview URL: https://b773861d.oasis-explorer.pages.dev
open, see footer "Version: aad8eec" ⚠️

[buberdds]

hmm how this is even possible that footer getBuildData has a different commit ?

[lukaw3d]

CI logs say: HEAD is now at aad8eec Merge 62f8165d829668803f55e405d4d33ddc2af61b37 into 365768cfb7e7d74ba7d4424989a8c3406bb8da91

Is github by default doing "merged results pipelines" (gitlab term)? :O

[lukaw3d]

I guess this is fine 🤷

[buberdds]

https://github.com/actions/checkout#checkout-pull-request-head-commit-instead-of-merge-commit

[lukaw3d]

that might work - even on push event

the other alternative is https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target but looks like it carries extra risk

[buberdds]

I will merge and disable until switch

[lukaw3d]

We should have message-cancelled too
see: #289 (comment)

from a cancelled run: https://github.com/oasisprotocol/explorer/actions/runs/4752003232/jobs/8441821763

[lukaw3d]

Fixed by #314