Skip to content

Commit

Permalink
Make sure the functionbeat.yml and the functionbeat.reference.yml (#8844
Browse files Browse the repository at this point in the history
)

Make sure the required options are the same on both files and also use the
same default name for the function.
  • Loading branch information
ph committed Nov 1, 2018
1 parent 2423c65 commit cfdea3d
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 2 deletions.
5 changes: 4 additions & 1 deletion x-pack/functionbeat/_meta/beat.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,13 @@
# Configure functions to run on AWS Lambda, currently we assume that the credentials
# are present in the environment to correctly create the function when using the CLI.
#
# Configure which S3 bucket we should upload the lambda artifact.
functionbeat.provider.aws.deploy_bucket: "functionbeat-deploy"

functionbeat.provider.aws.functions:
# Define the list of function availables, each function required to have a unique name.
# Create a function that accepts events coming from cloudwatchlogs.
- name: fn_cloudwatch_logs
- name: cloudwatch
enabled: false
type: cloudwatch_logs

Expand Down
5 changes: 4 additions & 1 deletion x-pack/functionbeat/functionbeat.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,13 @@
# Configure functions to run on AWS Lambda, currently we assume that the credentials
# are present in the environment to correctly create the function when using the CLI.
#
# Configure which S3 bucket we should upload the lambda artifact.
functionbeat.provider.aws.deploy_bucket: "functionbeat-deploy"

functionbeat.provider.aws.functions:
# Define the list of function availables, each function required to have a unique name.
# Create a function that accepts events coming from cloudwatchlogs.
- name: fn_cloudwatch_logs
- name: cloudwatch
enabled: false
type: cloudwatch_logs

Expand Down

0 comments on commit cfdea3d

Please sign in to comment.