fix: [UIE-9835] IAM - Remove all instances of update_user
#13198
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
aaleksee-akamai
approved these changes
Dec 12, 2025
Collaborator
Cloud Manager UI test results🎉 831 passing tests on test run #1 ↗︎
|
jdamore-linode
approved these changes
Dec 12, 2025
abailly-akamai
added a commit
that referenced
this pull request
Dec 16, 2025
This was referenced Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Description 📝
It appears that
update_useris a user level permission and not an account level permission. As such, not returned by<user>/account/permissions. This permission can't be given by any other role, so why it even exist is uncertain. Someone may know. Bottom line is this create a bug in the profile update UI once IAM got enabledChanges 🔄
update_userScope 🚢
Upon production release, changes in this PR will be visible to:
Target release date 🗓️
12/16/2025
How to test 🧪
Have a IAM enabled account with
account_adminrole.Reproduction steps
Verification steps
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 ✅