AWS devopsagent documentation change
Summary
Corrected indentation in Splunk integration code samples without functional changes
Security assessment
Formatting adjustments in API examples. The 'Authorization' header and security token handling remain unchanged, indicating no security fixes. Incident data structure is identical.
Diff
diff --git a/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-splunk.md b/devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-splunk.md index e41bb7d86..3007590a0 100644 --- a//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-splunk.md +++ b//devopsagent/latest/userguide/configuring-capabilities-for-aws-devops-agent-connecting-telemetry-sources-connecting-splunk.md @@ -118,6 +118,6 @@ Set the method and the headers - method: "POST", - headers: { - "Content-Type": "application/json", - "Authorization": "Bearer <Token>", - }, - + method: "POST", + headers: { + "Content-Type": "application/json", + "Authorization": "Bearer <Token>", + }, + @@ -129,10 +129,10 @@ Send the body as a JSON string. - eventType: 'incident'; - incidentId: string; - action: 'created' | 'updated' | 'closed' | 'resolved'; - priority: "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" | "MINIMAL"; - title: string; - description?: string; - timestamp?: string; - service?: string; - // The original event generated by service is attached here. - data?: object; + eventType: 'incident'; + incidentId: string; + action: 'created' | 'updated' | 'closed' | 'resolved'; + priority: "CRITICAL" | "HIGH" | "MEDIUM" | "LOW" | "MINIMAL"; + title: string; + description?: string; + timestamp?: string; + service?: string; + // The original event generated by service is attached here. + data?: object;