Addition related to API keys #264
Merged
Conversation
This file contains 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
alallema
force-pushed
the
keys
branch
2 times, most recently
from
561b562 to
a1aee65
Compare
bidoubiwa
reviewed
Feb 3, 2022
Comment on lines
+115
to
+117
| CreatedAt time.Time `json:"createdAt,omitempty"` | ||
| UpdatedAt time.Time `json:"updatedAt,omitempty"` | ||
| ExpiresAt *string `json:"expiresAt"` |
There was a problem hiding this comment.
It is normal that only expiresAt has a string?
There was a problem hiding this comment.
Yes, I will create an issue about it because there are two structs for handle key: Key and KeyParsed.
This one will not be used by the user it just allows me to recreate a Key with expirationAt that has the exact ISO-8601 and is a pointer because it could be set at nil in case you don't want to set and expirationAt
|
bors merge |
bors bot
added a commit
that referenced
this pull request
Feb 8, 2022
247: Changes related to the next MeiliSearch release (v0.25.0) r=alallema a=meili-bot Related to this issue: meilisearch/integration-guides#157 This PR: - gathers the changes related to the next MeiliSearch release (v0.25.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of MeiliSearch](https://github.com/meilisearch/MeiliSearch/releases). - might eventually contain test failures until the MeiliSearch v0.25.0 is out.⚠️ This PR should NOT be merged until the next release of MeiliSearch (v0.25.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/master/guides/pre-release-week.md) purpose._ Done: - #254 - #255 - #256 - #257 - #262 - #264 - #265 - #266 Co-authored-by: meili-bot <74670311+meili-bot@users.noreply.github.com> Co-authored-by: Amélie <alallema@users.noreply.github.com> Co-authored-by: alallema <amelie@meilisearch.com> Co-authored-by: bors[bot] <26634292+bors[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Breaking Changes
Granular management of API keys is now added to MeiliSearch. New methods have been created to manage this:
client.GetKeyget information about a specific API key.client.CreateKeycreate a new API key.client.DeleteKeydelete an API key.client.UpdateKeyupdate an API key.Modification:
client.GetKeys