[Cloud Security] Refactoring the limit error message for agentless agent (#203257)

This commit is contained in:
seanrathier 2024-12-06 14:20:33 -05:00 committed by GitHub
parent 354858264f
commit 1d3bf85d19
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -37,6 +37,15 @@ import { listFleetServerHosts } from '../fleet_server_host';
import type { AgentlessConfig } from '../utils/agentless';
import { prependAgentlessApiBasePathToEndpoint, isAgentlessEnabled } from '../utils/agentless';
interface AgentlessAgentErrorHandlingMessages {
[key: string]: {
[key: string]: {
log: string;
message: string;
};
};
}
class AgentlessAgentService {
public async createAgentlessAgent(
esClient: ElasticsearchClient,
@ -326,14 +335,12 @@ class AgentlessAgentService {
throw this.getAgentlessAgentError(action, error.message, traceId);
}
const ERROR_HANDLING_MESSAGES = this.getErrorHandlingMessages(agentlessPolicyId);
const ERROR_HANDLING_MESSAGES: AgentlessAgentErrorHandlingMessages =
this.getErrorHandlingMessages(agentlessPolicyId);
if (error.response) {
if (error.response.status in ERROR_HANDLING_MESSAGES) {
const handledResponseErrorMessage =
ERROR_HANDLING_MESSAGES[error.response.status as keyof typeof ERROR_HANDLING_MESSAGES][
action
];
const handledResponseErrorMessage = ERROR_HANDLING_MESSAGES[error.response.status][action];
this.handleResponseError(
action,
error.response,
@ -426,7 +433,7 @@ class AgentlessAgentService {
: new AgentlessAgentDeleteError(this.withRequestIdMessage(userMessage, traceId));
}
private getErrorHandlingMessages(agentlessPolicyId: string) {
private getErrorHandlingMessages(agentlessPolicyId: string): AgentlessAgentErrorHandlingMessages {
return {
400: {
create: {
@ -483,13 +490,7 @@ class AgentlessAgentService {
create: {
log: '[Agentless API] Creating the agentless agent failed with a status 429 for agentless policy, agentless agent limit has been reached for this deployment or project.',
message:
'the Agentless API could not create the agentless agent, you have reached the limit of agentless agents provisioned for this deployment or project. Consider removing some agentless agents and try again or use agent-based agents for this integration.',
},
// this is likely to happen when deleting agentless agents, but covering it in case
delete: {
log: '[Agentless API] Deleting the agentless deployment failed with a status 429 for agentless policy, agentless agent limit has been reached for this deployment or project.',
message:
'the Agentless API could not delete the agentless deployment, you have reached the limit of agentless agents provisioned for this deployment or project. Consider removing some agentless agents and try again or use agent-based agents for this integration.',
'you have reached the limit for agentless provisioning. Please remove some or switch to agent-based integration.',
},
},
500: {