Repository navigation
identity: credentials Update test sends only blob - #4013
Merged
Merged
Conversation
Keystone 2026.2 [1] restricts PATCH /v3/credentials/{id} to accept
only the blob field. The project_id, type, and user_id fields are now
immutable after creation.
Update unit and acceptance tests to only send blob in the update
request, matching the new Keystone schema. The SDK's UpdateOpts already
uses omitempty on all fields, so no code change is needed — users who
only set Blob will correctly send a valid request to both old and new
Keystone versions.
[1] https://review.opendev.org/c/openstack/keystone/+/1002330
github-actions
Bot
added
semver:patch
|
coverage: 63.594%. remained the same — shiftstack:fix-keystone-tests into gophercloud:main |
winiciusallan
approved these changes
Sep 16, 2026
|
Failed to backport PR to |
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.
Keystone 2026.2 [1] restricts PATCH /v3/credentials/{id} to accept only the blob field. The project_id, type, and user_id fields are now immutable after creation.
Update unit and acceptance tests to only send blob in the update request, matching the new Keystone schema. The SDK's UpdateOpts already uses omitempty on all fields, so no code change is needed — users who only set Blob will correctly send a valid request to both old and new Keystone versions.
[1] https://review.opendev.org/c/openstack/keystone/+/1002330