Fix token request validation - accept any username format
All checks were successful
Build And Test / build-and-push (push) Successful in 1m44s

- Change username field from EmailField to CharField in TokenRequestSerializer
- NHN Cloud API validates credentials, backend shouldn't restrict format
- Bump version to v0.0.2

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
2026-01-14 02:03:31 +09:00
parent 74eecafea4
commit 8b06504409
2 changed files with 4 additions and 3 deletions

View File

@ -17,8 +17,9 @@ class TokenRequestSerializer(serializers.Serializer):
help_text="NHN Cloud 테넌트 ID", help_text="NHN Cloud 테넌트 ID",
max_length=64, max_length=64,
) )
username = serializers.EmailField( username = serializers.CharField(
help_text="NHN Cloud 사용자 이메일", help_text="NHN Cloud 사용자 ID (이메일 또는 API 사용자 ID)",
max_length=255,
) )
password = serializers.CharField( password = serializers.CharField(
help_text="NHN Cloud API 비밀번호", help_text="NHN Cloud API 비밀번호",

View File

@ -1 +1 @@
v0.0.1 v0.0.2