Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Auto Import] Change internal API path to /internal #199384

Open
ebeahan opened this issue Nov 7, 2024 · 2 comments
Open

[Auto Import] Change internal API path to /internal #199384

ebeahan opened this issue Nov 7, 2024 · 2 comments
Assignees
@haetamoudi
Labels
bug Fixes for quality problems that affect the customer experience Feature:AutomaticImport Team:Security-Scalability Team label for Security Integrations Scalability Team

Comments

@ebeahan
Copy link
Member

ebeahan commented Nov 7, 2024

Summary

Currently Automatic Import internal HTTP APIs use the base path /api/integration_assistant.

Auto Imports internal APIs should follow the Kibana convention of an /internal prefix instead of /api.
@ebeahan ebeahan added bug Fixes for quality problems that affect the customer experience Feature:AutomaticImport Team:Security-Scalability Team label for Security Integrations Scalability Team labels Nov 7, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-scalability (Team:Security-Scalability)

@ebeahan ebeahan changed the title [Auto Import] Change API paths to /internal from /api [Auto Import] Change internal API path to /internal Nov 7, 2024
@ebeahan
Copy link
Member Author

ebeahan commented Nov 19, 2024

@kgeller suggested changing the entire path: /internal/automatic_import for 8.last and 9.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@haetamoudi haetamoudi

Labels
bug Fixes for quality problems that affect the customer experience Feature:AutomaticImport Team:Security-Scalability Team label for Security Integrations Scalability Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ebeahan @elasticmachine @haetamoudi