Feature/update authenticate specs #5270
Conversation
| export class AuthenticateApiKey { | ||
| id: Id | ||
| name?: Name | ||
| managed_by: AuthenticateApiKeyManagedBy |
There was a problem hiding this comment.
slightly verbose name to avoid a naming conflict that comes up when using ManagedBy:
ManagedBy is present in multiple namespaces: indices._types and security.authenticate
There was a problem hiding this comment.
Do you we have plans to add managed_by to other APIs? If yes it should be added under specification/security so that it's not specific to this API.
There was a problem hiding this comment.
I'll raise this internally but to my knowledge, this is specific to this api currently. Will refactor if we come back here again!
There was a problem hiding this comment.
Right, thank you! Actually, a refactor here would be a breaking change for some clients that expose the specification hierarchy, which is why I asked.
|
Following you can find the validation changes against the target branch for the APIs. No changes detected. You can validate these APIs yourself by using the |
Updating API spec for the
/_security/_authenticateAPI to add a couple of new fields,internalandmanaged_bythat are applicable to API Keys