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

Deprecate the action HTTP APIs #90378

Closed
mikecote opened this issue Feb 5, 2021 · 4 comments
Closed

Deprecate the action HTTP APIs #90378

mikecote opened this issue Feb 5, 2021 · 4 comments
Assignees
@gmmorris
Labels
blocked Feature:Actions Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Feb 5, 2021 •
edited by gmmorris
Loading

Blocked by #90376.

This is the second step of #90375. We should deprecate the action HTTP APIs that use the old terminology and request solution/application teams to switch over to the new APIs by 7.last. Don't forget docs and release notes.

For details on the introduction of the terminology see notes under #90375 (comment)
@mikecote mikecote added blocked Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. labels Feb 5, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

This was referenced Feb 5, 2021
Open
Closed
Closed
@gmmorris gmmorris self-assigned this Mar 4, 2021
@gmmorris
Copy link
Contributor

gmmorris commented Mar 4, 2021

The deprecation has been done as part of the same PR as #90376

This issue is now a reminder to contact the teams using these APIs and ask them to migrate by 7.last

@gmmorris
Copy link
Contributor

gmmorris commented Mar 9, 2021

Opened issues for the various teams using the deprecated APIs:

  1. Security Solution Migrate Security Solution to new Connectors APIs in place of deprecated APIs #94088
  2. Uptime Migrate Uptime to new Connectors APIs in place of deprecated APIs #94089

@gmmorris
Copy link
Contributor

I'm going to close this issue now as the APIs are officially marked as deprecated and two follow up issues have been opened for SecuritySolution & Uptime

@ymao1 ymao1 mentioned this issue Mar 30, 2021
Closed
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gmmorris gmmorris

Labels
blocked Feature:Actions Project:UnifiedAlertingArchitectureAndExperience Alerting team project for developing a unified alerting experience. Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@gmmorris @kobelb @mikecote @elasticmachine