DevHub Frontend CICD

[kj4ezj]

Following on devrel issue 134, @nsjames needs to be able to deploy new versions of the DevHub portal frontend (learn.eosnetwork.com) without my help. This ticket is to make a minimum viable product GitHub Action workflow that performs the following for the frontend on base branches or tags:

1. Builds the static site
2. Updates the contents of the S3 bucket
3. Triggers the CDN to invalidate the content at edge locations and load from the origin

See Also

• devrel issue 80 - Standup DevHub Infrastructure
• devrel issue 96 - DNS Mapping for learn.eosnetwork.com
• devrel issue 134 - Update DevHub Site
• devrel issue 135 - DevHub Frontend CICD
  • Pull Request 1 - .gitignore Updates
  • Pull Request 2 - Pin nodeJS Toolchain
  • Pull Request 3 - Add the MIT License to This Repo
  • Pull Request 4 - package.json + README.md Updates
  • Pull Request 5 - Moar Documentation
  • Pull Request 6 - Rename BACKEND_API to DEVHUB_BACKEND_API in the Environment
  • Pull Request 7 - DevHub Frontend CICD Pipeline - Build Part 1
  • Pull Request 8 - DevHub Frontend CICD Pipeline - Build Part 2
  • Pull Request 9 - Authenticate to AWS Using OIDC in GitHub Actions
  • Pull Request 10 - Add Contextual AWS Deployment to GitHub Actions
  • Pull Request 11 - Fix Production AWS Deployment
• devrel issue 137 - Encrypt DevHub Backend
• devhub issue 12 - Put AWS Resources into Terraform with a CICD Deployment
• devhub issue 13 - Document CICD System
• devhub issue 14 - Staging Environment
• devhub issue 15 - Backend CICD
• devhub issue 16 - Structures CICD
• devhub issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
• devhub issue 18 - Add BASH Linters for CICD Code
• devhub issue 19 - Include Test Suite in CICD

[kj4ezj]

Next Steps:

• Issue 12 - Put AWS Resources into Terraform with a CICD Deployment
• Issue 13 - Document CICD System
• Issue 14 - Staging Environment
• Issue 15 - Backend CICD
• Issue 16 - Structures CICD
• Issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
• Issue 18 - Add BASH Linters for CICD Code
• Issue 19 - Include Test Suite in CICD