Skip to content

Commit

Permalink
[M365 Defender] change connection_string to secret (#12112)
Browse files Browse the repository at this point in the history
Change property connection_string to be a secret like in the other integrations.
  • Loading branch information
SimonKoetting authored Dec 16, 2024
1 parent 5191d0c commit 9f84c20
Show file tree
Hide file tree
Showing 3 changed files with 8 additions and 2 deletions.
5 changes: 5 additions & 0 deletions packages/m365_defender/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,4 +1,9 @@
# newer versions go on top
- version: "2.17.1"
changes:
- description: Change connection_string to be a secret
type: bugfix
link: https://github.com/elastic/integrations/pull/12112
- version: "2.17.0"
changes:
- description: Do not remove `event.original` in main ingest pipeline.
Expand Down
3 changes: 2 additions & 1 deletion packages/m365_defender/data_stream/event/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -24,11 +24,12 @@ streams:
description: >-
We recommend using a dedicated consumer group for the azure input. Reusing consumer groups among non-related consumers can cause unexpected behavior and possibly lost events.
- name: connection_string
type: text
type: password
title: Connection String
multi: false
required: true
show_user: true
secret: true
description: >-
The connection string required to communicate with Event Hubs. See [Get an Event Hubs connection string](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string) to learn more.
- name: storage_account
Expand Down
2 changes: 1 addition & 1 deletion packages/m365_defender/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: "3.0.2"
name: m365_defender
title: Microsoft M365 Defender
version: "2.17.0"
version: "2.17.1"
description: Collect logs from Microsoft M365 Defender with Elastic Agent.
categories:
- "security"
Expand Down

0 comments on commit 9f84c20

Please sign in to comment.