-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Cloud Security] Handle critical errors returned from the Agentless API when creating and deleting agentless agents #195997
Open
seanrathier
wants to merge
8
commits into
elastic:main
Choose a base branch
from
seanrathier:10657-agentless-handle-critical-error-statuses
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+857
−135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seanrathier
force-pushed
the
10657-agentless-handle-critical-error-statuses
branch
from
October 17, 2024 13:25
ed2b902
to
917cec7
Compare
seanrathier
added
8.17 candidate
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
Team:Cloud Security
Cloud Security team related
ci:project-deploy-security
Create a Security Serverless Project
release_note:skip
Skip the PR/issue when compiling release notes
labels
Oct 17, 2024
seanrathier
changed the title
10657 agentless handle critical error statuses
[Cloud Security] Handle critical errors returned from the Agentless API when creating and deleting agentless agents
Oct 17, 2024
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
botelastic
bot
added
the
Team:Fleet
Team label for Observability Data Collection Fleet team
label
Oct 17, 2024
Pinging @elastic/fleet (Team:Fleet) |
juliaElastic
approved these changes
Oct 18, 2024
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
seanrathier
force-pushed
the
10657-agentless-handle-critical-error-statuses
branch
from
October 18, 2024 15:32
869782e
to
d8ddf42
Compare
💚 Build Succeeded
Metrics [docs]
History
cc @seanrathier |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
8.17 candidate
backport:prev-minor
Backport to (8.x) the previous minor version (i.e. one version back from main)
ci:project-deploy-security
Create a Security Serverless Project
release_note:skip
Skip the PR/issue when compiling release notes
Team:Cloud Security
Cloud Security team related
Team:Fleet
Team label for Observability Data Collection Fleet team
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
We are adding more defined error handling on the statuses returned from the Agentless API. This includes some changes to the data and messages being logged and the error that is thrown to the user.
We've also refactored the code to have the agentless agent
create
anddelete
actions share the same handling function.Checklist
Delete any items that are not applicable to this PR.