-
Notifications
You must be signed in to change notification settings - Fork 474
[AWS] [CloudWatch] Improve description to highlight lastSync option #14733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AWS] [CloudWatch] Improve description to highlight lastSync option #14733
Conversation
5fa8e79
to
bcf7f20
Compare
228082d
to
78f12db
Compare
@@ -216,7 +216,7 @@ streams: | |||
required: false | |||
default: beginning | |||
show_user: true | |||
description: Allows user to specify if this input should read log files from the beginning or from the end. | |||
description: Specify if the input should start reading logs from from the `beginning` (oldest log entry), `end` (newest log entry), or `lastSync` (last successful read timestamp if input ran before). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
description: Specify if the input should start reading logs from from the `beginning` (oldest log entry), `end` (newest log entry), or `lastSync` (last successful read timestamp if input ran before). | |
description: Specify if the input should start reading logs from the `beginning` (oldest log entry), `end` (newest log entry), or `lastSync` (last successful read timestamp if input ran before). |
(throughout)
Also consider s/if/whether/
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks will fix this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed this with - 91156f0 :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SSI files LGTM
🚀 Benchmarks reportTo see the full report comment with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co> # Conflicts: # packages/aws/changelog.yml
Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>
91156f0
to
dd7ed62
Compare
💚 Build Succeeded
History
|
|
Package aws - 3.13.4 containing this change is available at https://epr.elastic.co/package/aws/3.13.4/ |
Package aws_bedrock - 1.2.3 containing this change is available at https://epr.elastic.co/package/aws_bedrock/1.2.3/ |
Package aws_logs - 1.8.2 containing this change is available at https://epr.elastic.co/package/aws_logs/1.8.2/ |
Package aws_mq - 0.9.1 containing this change is available at https://epr.elastic.co/package/aws_mq/0.9.1/ |
Proposed commit message
Improve the description of
start_position
field withlastSync
configuration option.Checklist
changelog.yml
file.Related issues
Related elastic/beats#43251
Screenshots