Skip to content

Conversation

@lcchrty
Copy link
Member

@lcchrty lcchrty commented May 22, 2025

Fixes #1918

What changes did you make and why did you make them ?

  • Applied changes from 1497-incubator branch h/t @ale210
  • The updated workflow:
    • modernizes the GitHub Actions jobs
    • provides enhanced security practices by assuming roles rather than using secrets
    • Simplifies jobs and steps to remove

chipcorncob and others added 30 commits May 12, 2025 19:57
update aws-actions/configure-aws-credentials to v3
update aws-actions/configure-aws-credentials to v3
add force deployment step for missing service
updated AWS_APP_NAme to match previous passed test
match devops incubator test
updated build and push to ECR steps
@lcchrty lcchrty marked this pull request as ready for review May 25, 2025 20:53
@lcchrty lcchrty requested a review from trillium May 25, 2025 20:53
@JackHaeg JackHaeg mentioned this pull request May 26, 2025
4 tasks
@JackHaeg
Copy link
Member

@trillium Please review this PR whenever you have a moment :) Once fixed, then we should potentially rebuild PROD with the latest feature updates for Bonnie to review on Thursday's call.

@lcchrty
Copy link
Member Author

lcchrty commented May 27, 2025

@JackHaeg @trillium Alex (@ale210) on the DevOps team is working on migrating the prod env as well, so it may be worth it to sync with him!

Copy link
Member

@trillium trillium left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey hey, stoked that this is working, there's a knick-knack or two that need to be addressed though, please see comments.

I see that the deploy works though (re checking out the actions) thank you!!!

fi
outputs:
AWS_APPENV: ${{ env.AWS_APPENV }}
AWS_APPENV: ${{ env.AWS_APPENV }}git checkou
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure this is a typo

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep! fixed.

@JackHaeg
Copy link
Member

JackHaeg commented Jun 3, 2025

@lcchrty When you have a moment, can you please implement the changes requested by @trillium? Once complete, we can then rebuild Dev & (potentially) Prod as a test

@lcchrty
Copy link
Member Author

lcchrty commented Jun 5, 2025

@trillium @JackHaeg changes made and fingers crossed this is good to go!

@JackHaeg
Copy link
Member

Thanks @lcchrty!!

@trillium can you please review this PR when you have a moment?

@JackHaeg
Copy link
Member

@trillium Can you please review this PR this week to unblock rebuilding Dev / Prod?

@trillium trillium requested a review from Copilot June 18, 2025 20:21
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR modernizes the frontend deployment workflow by switching to AWS OIDC role assumptions, updating naming and paths, and streamlining build/deploy steps.

  • Switches aws-actions/configure-aws-credentials to v3 with OIDC role assumption and removes static secrets
  • Updates AWS_APP_NAME and Dockerfile path, and consolidates Docker build into a custom shell step
  • Replaces multiple ECS action steps with a single AWS CLI update-service call
Comments suppressed due to low confidence (3)

.github/workflows/aws-frontend-deploy.yml:18

  • The Dockerfile path and build context may be mismatched: you cd into ${{ env.DOCKER_PATH }} (client) but reference Dockerfile.prod at the repo root. Either move the Dockerfile into the client directory or update DOCKER_PATH to . so the file is found in the build context.
  DOCKERFILE: Dockerfile.prod

.github/workflows/aws-frontend-deploy.yml:63

  • Consider using the ${{ env.AWS_REGION }} variable here instead of hardcoding us-west-2, to keep region configuration consistent and centralized.
          aws-region: us-west-2

.github/workflows/aws-frontend-deploy.yml:73

  • [nitpick] The ls command appears to be leftover debugging output and isn’t required for the build step. Removing it will clean up the workflow logs.
          ls

Copy link
Member

@trillium trillium left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved!

Thanks for getting this working again @lcchrty

AWS_APP_NAME: vrms-frontend
AWS_REGION: us-west-2
DOCKERFILE: client/Dockerfile.prod
DOCKERFILE: Dockerfile.prod
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there, can you clarify which file you're pointing to here? I don't see a Dockerfile.prod in the base dir of the monorepo

@trillium trillium merged commit 8990c1b into development Jun 18, 2025
8 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix Frontend Build Action

5 participants