-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[8.12] Rename some alert -> rule and action -> connector terminology in the code #168861
Labels
response-ops-ec-backlog
ResponseOps E&C backlog
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
technical debt
Improvement of the software architecture and operational architecture
Comments
mikecote
added
the
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
label
Oct 13, 2023
Pinging @elastic/response-ops (Team:ResponseOps) |
github-project-automation
bot
moved this to Awaiting Triage
in AppEx: ResponseOps - Execution & Connectors
Oct 13, 2023
mikecote
changed the title
Rename some alert -> rule and action -> connector terminology in the code
[8.12] Rename some alert -> rule and action -> connector terminology in the code
Oct 13, 2023
mikecote
added
the
technical debt
Improvement of the software architecture and operational architecture
label
Oct 13, 2023
mikecote
moved this from Awaiting Triage
to Todo
in AppEx: ResponseOps - Execution & Connectors
Oct 13, 2023
ymao1
added a commit
that referenced
this issue
Dec 18, 2023
…teAlert` -> `partiallyUpdateRule` (#172859) Towards #168861 ## Summary * Adding `RULE_SAVED_OBJECT_TYPE = 'alert'` and using it everywhere * Rename `partiallyUpdateAlert` fn to `partiallyUpdateRule` Using this const in place of `alert` changed so many files that I limited this PR to just these changes. --------- Co-authored-by: kibanamachine <[email protected]>
doakalexi
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Feb 6, 2024
doakalexi
moved this from In Progress
to Todo
in AppEx: ResponseOps - Execution & Connectors
Feb 12, 2024
mikecote
moved this from Todo
to In Progress
in AppEx: ResponseOps - Execution & Connectors
Feb 14, 2024
doakalexi
moved this from In Progress
to In Review
in AppEx: ResponseOps - Execution & Connectors
Mar 19, 2024
doakalexi
moved this from In Review
to Todo
in AppEx: ResponseOps - Execution & Connectors
Mar 19, 2024
doakalexi
added a commit
that referenced
this issue
Mar 20, 2024
) Related to #168861 ## Summary This is a tech debt issue that I made a little progress on, I made some changes to rename alert -> rule. It's an ongoing task, but I made a PR for my changes so I can release the issue back to the iteration. Nothing to verify, just make sure that the build passes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
response-ops-ec-backlog
ResponseOps E&C backlog
Team:ResponseOps
Label for the ResponseOps team (formerly the Cases and Alerting teams)
technical debt
Improvement of the software architecture and operational architecture
We should timebox up to 2 days in 8.12 to continue renaming the terminology in our codebase where it is out of date.
Some examples include:
partially_update_alert.ts
where it's really partially updating a ruleconst RULE_SO_TYPE = 'alert';
so we only seealert
once with a comment on top.. and re-use it when calling different functions likecreateInternalRepository([RULE_SO_TYPE])
The text was updated successfully, but these errors were encountered: