feat(IAM Identity): add support for IDP sharing/settings - #331
Merged
Conversation
hariarla
force-pushed
the
enable_idp_sharing
branch
from
June 28, 2026 15:33
bddd336 to
8efbeb4
Compare
Signed-off-by: Hari K Arla <hariarla@in.ibm.com>
hariarla
force-pushed
the
enable_idp_sharing
branch
from
June 28, 2026 19:50
8efbeb4 to
1a4c911
Compare
pyrooka
self-requested a review
July 22, 2026 11:56
pyrooka
changed the title
ibm-devx-sdk
pushed a commit
that referenced
this pull request
Jul 22, 2026
# [0.77.0](v0.76.0...v0.77.0) (2026-07-22) ### Features * **IAM Identity:** add support for IDP sharing/settings([#331](#331)) ([b1025a0](b1025a0))
|
🎉 This PR is included in version 0.77.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
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