Future Work
Next steps to streamline deployment and enhance user customization include:
Detect Stack Type
Section titled “Detect Stack Type”Automatically detect the correct stack by inspecting the user’s repo, rather than requiring stack type selection.
Streamline Redeployment Authentication
Section titled “Streamline Redeployment Authentication”For authenticating GitHub Actions to access the users’ AWS resources during redeployment, replace the current system that utilizes GitHub Actions Secrets with OpenID Connect (OIDC). OIDC is a more streamlined solution for managing permissions that would reduce the manual setup required from the user.
Expand Infrastructure Configurability
Section titled “Expand Infrastructure Configurability”Offer additional customization settings, such as specifying a build script or infrastructure details. These details could include Fargate virtual CPU count or number of instances.
Deploy Preview Environments
Section titled “Deploy Preview Environments”Deploy separate, ephemeral environments to allow developers to preview and test changes to their application. These could be triggered by pull requests to main, whereas the current redeployment workflow triggers on pushes and merges to main.
De-clutter Deployment Console Output
Section titled “De-clutter Deployment Console Output”Replace the verbose default console output by CDK during deployment with clear and concise custom outputs.