feat(IAM Identity): add new account settings - #306
Merged
Conversation
Signed-off-by: Daniel Byrne <byrne.dan01@gmail.com>
Daniel-Byrne
force-pushed
the
identity-effective
branch
from
September 25, 2025 15:40
7db1a30 to
eff4101
Compare
Daniel-Byrne
marked this pull request as ready for review
September 26, 2025 09:30
pyrooka
changed the title
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Oct 1, 2025
# [0.69.0](v0.68.3...v0.69.0) (2025-10-01) ### Features * **IAM Identity:** add new account settings ([#306](#306)) ([eb18405](eb18405))
|
🎉 This PR is included in version 0.69.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
3 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.
PR summary
Main change -> added two new attributes (
restrict_user_list_visibilityandrestrict_user_domains) into the Account Settings APIs, all other changes are a result of some rejigging of our API docs to reduce duplication.PR Checklist
Please make sure that your PR fulfills the following requirements:
Current vs new behavior
Does this PR introduce a breaking change?
Other information
Examples
Integration
