Conversation
* chore: docker login step의 DOCKERHUB_USERNAME 환경 변수를 secrets 참조 대신 env 값으로 통일 * chore: docker login step의 DOCKERHUB_ACCESS_KEY 환경 변수 이름 DOCKERHUB_ACCESS_TOKEN 으로 변경
chaiminwoo0223
approved these changes
Jun 19, 2025
Contributor
chaiminwoo0223
left a comment
There was a problem hiding this comment.
변경된 내용 확인했습니다. 머지 부탁드립니다.
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.
📌 작업 내용 및 특이사항
✅ develop 배포 워크플로우 수정
develop_build_deploy워크플로우의dockerhub login step에서 설정한 환경 변수를 수정했습니다.DOCKERHUB_USERNAME은 Github Actions 워크플로 내에서env:로 관리하는데, secrets 로 참조하고 있어 env 값으로 통일시켰습니다.DOCKERHUB_ACCESS_KEY->DOCKERHUB_ACCESS_TOKEN으로 이름을 변경했습니다.🌱 관련 이슈
🔍 참고사항(선택)
docker login steps에서 환경 변수 이름 이슈로 에러가 발생했지만, 임시로 secrets 에DOCKERHUB_USERNAME과DOCKERHUB_ACCESS_KEY값을 등록해 에러를 해결했습니다.swagger가 정상적으로 동작하는 걸 확인했습니다.DOCKERHUB_USERNAME,DOCKERHUB_ACCESS_KEY값은 삭제하겠습니다.📚 기타(선택)