-
Notifications
You must be signed in to change notification settings - Fork 145
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
Followup on #2861 #2923
Followup on #2861 #2923
Conversation
logger.debug( | ||
"Agent configuration is not ready to create a connector record." | ||
) |
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.
Can we update the copy to provide more specific detail on what's going on? How can configuration be not ready? Is it gonna be happening a lot?
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.
Is it gonna be happening a lot?
It should not be happening at all... just here to verify that the config is 100% what we expect this to be. We only call ensure_connector_records_exist
once we have ES output from the agent protocol checkin.
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.
Looks good, left a couple comments
…-python into jedrazb-2861-followup
Co-authored-by: Artem Shelkovnikov <[email protected]>
💔 Failed to create backport PR(s)The backport operation could not be completed due to the following error: The backport PRs will be merged automatically after passing CI. To backport manually run: |
Follow up on unaddressed comments from #2861
Addressed items:
connector_exists
to ConnectorIndex classgenerate_random_id
to utils class