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.

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

[ResponseOps][Rules] Version update api key rule route #188722

Merged
merged 5 commits into from
Jul 24, 2024

Conversation

adcoelho
Copy link
Contributor

Summary

Parent Issue: #187572

Versions the POST /rule/{id}/_update_api_key endpoint.

Checklist

@adcoelho adcoelho added release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework v8.16.0 labels Jul 19, 2024
@adcoelho adcoelho self-assigned this Jul 19, 2024
@adcoelho adcoelho requested a review from a team as a code owner July 19, 2024 08:58
@elasticmachine
Copy link
Contributor

Pinging @elastic/response-ops (Team:ResponseOps)

@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

✅ unchanged

History

cc @adcoelho

Copy link
Member

@umbopepato umbopepato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@@ -164,7 +164,7 @@ export class RulesClient {
public bulkDisableRules = (options: BulkDisableRulesRequestBody) =>
bulkDisableRules(this.context, options);

public updateApiKey = (options: { id: string }) => updateApiKey(this.context, options);
public updateApiKey = (params: { id: string }) => updateApiKey(this.context, params);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's rename this to updateRuleApiKey so update_api_key.ts -> update_rule_api_key.ts

} from '../../../../../common/routes/rule/apis/update_api_key';
import { ILicenseState, RuleTypeDisabledError } from '../../../../lib';
import { verifyAccessAndContext } from '../../../lib';
import { AlertingRequestHandlerContext, BASE_ALERTING_API_PATH } from '../../../../types';

export const updateRuleApiKeyRoute = (
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rename this file update_rule_api_key_route.ts

@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @adcoelho

@adcoelho adcoelho merged commit 317154d into elastic:main Jul 24, 2024
37 checks passed
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting Feature:Alerting/RulesFramework Issues related to the Alerting Rules Framework release_note:skip Skip the PR/issue when compiling release notes Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants