[ML] Include authorization info in responses when creating jobs#87950
Merged
droberts195 merged 4 commits intoelastic:masterfrom Jun 23, 2022
Merged
[ML] Include authorization info in responses when creating jobs#87950droberts195 merged 4 commits intoelastic:masterfrom
droberts195 merged 4 commits intoelastic:masterfrom
Conversation
elastic#87884 added authorization information to the datafeed and data frame analytics job configs returned by listing them, but not to the ones returned from creating or updating them. For consistency it's best that the same fields are present in both places.
Collaborator
|
Pinging @elastic/clients-team (Team:Clients) |
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
Author
11 tasks
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.
#87884 added
authorization information to the datafeed and data frame
analytics job configs returned by listing them, but not to
the ones returned from creating or updating them. For
consistency it's best that the same fields are present in
both places.