Identity v3: Adding ExpiresAt and DeletedAt fields to Trust results#1857
Merged
jtopjian merged 1 commit intogophercloud:masterfrom Feb 18, 2020
Merged
Conversation
|
Build succeeded.
|
72270ed to
33790ff
Compare
33790ff to
a440bb2
Compare
a440bb2 to
125340a
Compare
|
Build succeeded.
|
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
2 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.
For #1642
deleted_at: https://github.com/openstack/keystone/blob/04316beecc0d20290fb36e7791eb3050953c1011/keystone/trust/backends/sql.py#L34expires_at: https://github.com/openstack/keystone/blob/589152d094b248da81dc88db2449fb560985ae8b/keystone/trust/schema.py#L42-L44I'm not sure why
deleted_atisn't inschema.py, but it's a valid field that shows up in the API response.