Add workflow to mirror official lighthouse image to ECR - #2
Open
felixll3 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
workflow_dispatch) workflowsync-official-image-to-ecrthat pulls an official lighthouse image (e.g.sigp/lighthouse:vX.Y.Z) and pushes it to553885929720.dkr.ecr.us-east-1.amazonaws.com/lighthouse.ubuntu-22.04), not self-hosted — this repo is public, and the org's self-hosted runner groups (Prod/QA) don't allow public repos.Still needed before this can run
This repo currently has no AWS credentials configured. The workflow expects:
secrets.AWS_ACCESS_KEY_IDsecrets.AWS_SECRET_ACCESS_KEYwith
ecr:GetAuthorizationToken+ push permissions on553885929720.dkr.ecr.us-east-1.amazonaws.com/lighthouse. Someone with access to that account needs to add these as repo (or org, scoped to this repo) secrets. OIDC role assumption would be the more durable alternative to static keys, but needs a trust-policy change on the AWS side first.Test plan
AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEYsecrets with ECR push accesssource_image=sigp/lighthouse:<version>,ecr_tag=<version>