Skip to content
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

Merged
merged 1 commit into from
Dec 10, 2020

Conversation

nibalizer
Copy link
Contributor

@nibalizer nibalizer commented Nov 23, 2020

Fixes: #1406

Signed-off-by: Spencer Krum [email protected]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

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?:

BREAKING CHANGE: Users who run Falco without a config file will be unable to do that any more, Falco now expects a configuration file to be passed all the times. Developers may need to adjust their processes.

Copy link
Member

@leogr leogr left a 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).

userspace/falco/configuration.h Outdated Show resolved Hide resolved
@poiana poiana added the lgtm label Dec 9, 2020
@poiana
Copy link
Contributor

poiana commented Dec 9, 2020

LGTM label has been added.

Git tree hash: a2b6bc20469674478f2d0fc3575f8b15ddeff8d1

@poiana poiana added the approved label Dec 9, 2020
Copy link
Contributor

@fntlnz fntlnz left a 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

@poiana
Copy link
Contributor

poiana commented Dec 10, 2020

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana poiana merged commit 32daac3 into falcosecurity:master Dec 10, 2020
@fntlnz
Copy link
Contributor

fntlnz commented Dec 10, 2020

/milestone 0.27.0

@poiana poiana added this to the 0.27.0 milestone Dec 10, 2020
@fntlnz
Copy link
Contributor

fntlnz commented Dec 10, 2020

Updated the release notes indicating that this is a breaking change.

@nibalizer nibalizer deleted the fix_1406 branch December 10, 2020 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

segmentation fault when using -o and no config file
4 participants