Skip to content

Commit

Permalink
[azure_frontdoor] Add storage_account_container variables (#12151)
Browse files Browse the repository at this point in the history
Added to the manifests of both data streams.
Already used by the input config for the `access` data stream.
Usage added in the input config for the `waf` data stream.
  • Loading branch information
chrisberkhout authored Dec 18, 2024
1 parent 5220ddf commit 0e87805
Show file tree
Hide file tree
Showing 5 changed files with 30 additions and 2 deletions.
6 changes: 6 additions & 0 deletions packages/azure_frontdoor/changelog.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,9 @@
# newer versions go on top
- version: "2.1.2"
changes:
- description: Add `storage_account_container` variables.
type: bugfix
link: https://github.com/elastic/integrations/pull/12151
- version: "2.1.1"
changes:
- description: Change connection_string to be a secret
Expand Down
8 changes: 8 additions & 0 deletions packages/azure_frontdoor/data_stream/access/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,14 @@ streams:
type: bool
multi: false
default: false
- name: storage_account_container
type: text
title: Storage Account Container
multi: false
required: false
show_user: false
description: >
The storage account container where the integration stores the checkpoint data for the consumer group. It is an advanced option to use with extreme care. You MUST use a dedicated storage account container for each Azure log type (activity, sign-in, audit logs, and others). DO NOT REUSE the same container name for more than one Azure log type. See [Container Names](https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names) for details on naming rules from Microsoft. The integration generates a default container name if not specified.
- name: processors
type: yaml
title: Processors
Expand Down
Original file line number Diff line number Diff line change
@@ -1,10 +1,16 @@
{{#if connection_string}}
connection_string: {{connection_string}}
{{/if}}
{{#if storage_account_container }}
storage_account_container: {{storage_account_container}}
{{else}}
{{#if eventhub}}
eventhub: {{eventhub}}
storage_account_container: frontdoor-waf-{{eventhub}}
{{/if}}
{{/if}}
{{#if eventhub}}
eventhub: {{eventhub}}
{{/if}}
{{#if consumer_group}}
consumer_group: {{consumer_group}}
{{/if}}
Expand Down
8 changes: 8 additions & 0 deletions packages/azure_frontdoor/data_stream/waf/manifest.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,14 @@ streams:
type: bool
multi: false
default: false
- name: storage_account_container
type: text
title: Storage Account Container
multi: false
required: false
show_user: false
description: >
The storage account container where the integration stores the checkpoint data for the consumer group. It is an advanced option to use with extreme care. You MUST use a dedicated storage account container for each Azure log type (activity, sign-in, audit logs, and others). DO NOT REUSE the same container name for more than one Azure log type. See [Container Names](https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names) for details on naming rules from Microsoft. The integration generates a default container name if not specified.
- name: processors
type: yaml
title: Processors
Expand Down
2 changes: 1 addition & 1 deletion packages/azure_frontdoor/manifest.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
format_version: "3.0.2"
name: azure_frontdoor
title: "Azure Frontdoor"
version: "2.1.1"
version: "2.1.2"
description: "This Elastic integration collects logs from Azure Frontdoor."
type: integration
categories:
Expand Down

0 comments on commit 0e87805

Please sign in to comment.