feat: pre-release candidate

[ap0nia]

Features

• Construct-centric configuration.
  • Constructs are AWS's implementation of classes that can be used to represent (cloud) architecture, used in AWS's CDK and Terraform's CDKTF
• GitHub event handling: will offer CI/CD event callbacks that can be invoked following stack deployments, destructions, etc.
  • CI/CD integrations with deployments; after deploying a stack, it will be viewable in GitHub's "deployments" tab
  • e.g. commenting staging URLs
• Full-featured application constructs
  • API - focused on supporting PeterPortal API's backend deployment
  • Static Site - focused on supporting PeterPortal API's Docusaurus documentation deployment, and maybe basic static sites like AntAlamanac
  • SSR Site - NextJS and SvelteKit (post-release)
• Terraform > CloudFormation! (post-release + proposal) :^)

Stuff I'd probably be working on

• Implement methods for the API stack

  • dev: starts an ExpressJS development server
  • deploy: deploys the stacks created in the root config
  • destroy: destroys the stacks created in the root config

• Static Site construct

  • Maybe invoke the Docusaurus commands?
  • Write the constructs to allocate CloudFront and S3

• GitHub event hooks

  • On staging PR update (deploy)
  • On staging PR closed (destroy)
  • On production push (deploy)

Previous Stuff

# Summary
Proof of concept for fully managing our CI/CD processes in a 100% programmatic way using GitHub actions's JS api.

# TODO
- [x] Add some sort of description or metadata to the deployment statuses; every deployment creates 2 websites, so need to distinguish between the two
resolved by deploying to two different environments: staging - api and staging - docs, should be same for prod
- [x] Workflow files relating to deployment can be handled within Node
~~ - [x] stabilize (on all deployments): busy wait for CloudFormation when it's in the middle of updating
- [x] clean-up (on PR closed): invoke cdk destroy to clean up resources used for previews, then mark deployment status as inactive

[github-actions]

🚀 Staging instances deployed!

API - https://staging-61.api-next.peterportal.org

Docs - https://staging-61-docs.api-next.peterportal.org

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

[github-actions]

🚀 Staging instances deployed!

API -

Docs -

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

Docs - https://staging-61-docs.api-next.peterportal.org

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

Docs - https://staging-61-docs.api-next.peterportal.org

[github-actions]

🚀 Staging instances deployed!

API - https://g6qjhy7lu3.execute-api.us-east-1.amazonaws.com/prod/

Docs - https://staging-61-docs.api-next.peterportal.org

[ap0nia]

Will be closing and starting a separate dev-ops repository with these concepts 🤓