-
Notifications
You must be signed in to change notification settings - Fork 393
fix: [UIE-9063] - IAM Add User FE validation and schema improvement #12687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| onClick={() => setIsCreateDrawerOpen(true)} | ||
| sx={{ | ||
| maxWidth: '120px', | ||
| }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hana-akamai
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like devcloud has some issues right now so I wasn't able to create an actual user but validation looks good
Unrelated, I noticed an issue with bad grant calls for each user so I created M3-10478 to look into that
Cloud Manager UI test results🔺 1 failing test on test run #5 ↗︎
Details
TroubleshootingUse this command to re-run the failing tests: pnpm cy:run -s "cypress/e2e/core/linodes/linode-storage.spec.ts" |
|||||||||||||||||


Description 📝
The front-end validation was missing from the IAM
CreateUserdrawer, resulting on waiting for an API response and getting a rather unhelpful generic response ("Invalid username or email address").I added the missing yup resolver (which is also used in the legacy /account/users CreateUser drawer). In addition I improved the error messaging and validation schema based on what the API does, see:
ApiNext>validators>username_validator.pyChanges 🔄
CreateUserdrawerScope 🚢
Upon production release, changes in this PR will be visible to:
Target release date 🗓️
8/26/2025
Preview 📷
How to test 🧪
Prerequisites
IAM enabled account
Reproduction steps
Verification steps
💡 in addition:
Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅