-
Notifications
You must be signed in to change notification settings - Fork 8.5k
[ResponseOps][Connector V2] Make getAxiosInstance function available from the action client
#244619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
getAxiosInstance function available from the action client
75b811a to
63ce0b3
Compare
b931ed7 to
9bee84f
Compare
ymao1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Would be good to see a functional test that tests getting a preconfigured axios instance using the actions client.
...shared/actions/server/application/connector/methods/get_axios_instance/get_axios_instance.ts
Show resolved
Hide resolved
| }); | ||
|
|
||
| // check to see if it's in memory connector before fetching secrets | ||
| const inMemoryAction = inMemoryConnectors.find( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: is there a way to set the flag in the above check for inmemory connector?
...d/actions/server/application/connector/methods/get_axios_instance/get_axios_instance.test.ts
Outdated
Show resolved
Hide resolved
|
Pinging @elastic/response-ops (Team:ResponseOps) |
💚 Build Succeeded
Metrics [docs]
History
cc @adcoelho |
Closes #243808
Summary
Makes the utility function
getAxiosInstanceWithAuthaccessible outside the plugin via theactionsClient.For a given connector ID, this function validates the secrets and returns an axios instance properly configured with authentication.