Repository navigation
저장된 API key 폐기 시 실제 복구 순서 안내 - #149
Merged
Merged
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.
저장된 API key가 provider에서 폐기돼도
model setup은 그 key를 다시 읽으므로, 재설정만 권하면 같은 인증 실패가 반복된다. 인증 거절 안내에model logout PROFILE뒤model setup --name PROFILE을 명시하고, key 참조 누락도 실제 profile 이름을 골라 재설정하도록 안내한다. Environment key 우선순위는 문서에 함께 적었다.표시 문구와 문서만 바꾸며 credential 접근·삭제·저장, 오류 코드와 exit code는 그대로다. rc.7 태그 생성 전 보완이다. fmt·Clippy(all targets)·공개 문서 검사와 diff 검토를 통과했다. 기존 실행 경로는 #148의 Rust800개·첫 사용3개 layout 검증을 따르며 최종 source는 PR/main CI에서 다시 검사한다.