-
Notifications
You must be signed in to change notification settings - Fork 919
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
Better handle not having a config file #1494
Conversation
05300eb
to
2249afa
Compare
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.
SGTM and I agree to do not allow to start Falco without a config file.
What do @falcosecurity/maintainers think?
PS
Just found a tiny indentation issue (see below).
Fixes: falcosecurity#1406 Signed-off-by: Spencer Krum <nibz@spencerkrum.com>
LGTM label has been added. Git tree hash: a2b6bc20469674478f2d0fc3575f8b15ddeff8d1
|
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! Great job @nibalizer
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fntlnz, leogr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/milestone 0.27.0 |
Updated the release notes indicating that this is a breaking change. |
Fixes: #1406
Signed-off-by: Spencer Krum nibz@spencerkrum.com
What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area engine
What this PR does / why we need it:
When there is a config file that can't be read and a command line config set, that can create a seg fault. Instead of supporting the use case where the user doesn't have a config file, force the user to provide a config file and stop supporting a no-config-file case.
Which issue(s) this PR fixes:
Fixes # 1406
Special notes for your reviewer:
Does this PR introduce a user-facing change?: