Repository navigation
fix: kure_retriever CI가 :latest push에서 매번 실패하던 문제 수정 - #84
Merged
Merged
Conversation
Both real CI runs of the "Build and push KURE retriever Lambda image" job after the ECR immutable-tag policy was in place failed at "docker push $LATEST_URI" with "tag invalid: ... immutable" - meaning the job's actual deploy step (update-function-code) never ran, so the Lambda kept running stale code despite CI reporting activity. :latest was never actually needed past the first bootstrap - Terraform's image_uri reference to it is only read once at resource creation and then ignored via lifecycle.ignore_changes; every real deploy already goes through the versioned tag + update-function-code step below. Dropping the :latest push (rather than ignoring its failure) keeps the immutable-tag policy meaningful instead of quietly defeating it.
jeongmin1999
self-requested a review
July 4, 2026 06:01
jeongmin1999
approved these changes
Jul 4, 2026
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.
문제
PR #82, #83 머지 후 CI(
ai-ecr-push.yaml)의 "Build and push KURE retriever Lambda image" job이 둘 다docker push \$LATEST_URI단계에서 실패했습니다:```
tag invalid: The image tag 'latest' already exists in the 'utterai-kure-retriever'
repository and cannot be overwritten because the tag is immutable.
```
이 job이 실패하면서 뒤 단계인 "Deploy image to Lambda"(
update-function-code)가 실행 안 됐고, 버전 태그 이미지는 ECR에 정상 push됐는데도 실제 Lambda 코드는 갱신 안 되는 상태가 반복됐습니다 (PR #83의 웜업 수정도 이 때문에 CI로는 배포 안 돼서 수동으로update-function-code를 직접 실행해 확인했습니다).원인과 수정
utterai-kure-retrieverECR 리포지토리는 버전 관리를 강제하려고imageTagMutability=IMMUTABLE로 설정돼 있는데, CI는 매 실행마다:latest를 덮어쓰려고 시도해서 두 번째 실행부터 항상 실패했습니다.:latest는 사실 최초 부트스트랩(Terraform이 Lambda를 처음 생성할 때image_uri로 참조) 이후로는 전혀 안 쓰입니다 -lifecycle.ignore_changes로 무시되고, 실제 배포는 전부 버전 태그 +update-function-code로 이뤄지기 때문입니다.:latestpush를 아예 없앴습니다 (실패를 무시하는 방식은 immutable 정책 자체를 무력화하므로 채택하지 않았습니다).검증
Test plan
lambda/kure_retriever/**변경에서 이 job이 끝까지(Deploy 단계 포함) 성공하는지 확인