Skip to content

Allow include statement to succeed even if nothing matches #180

@shartge

Description

@shartge

For Debian I would like to rework the default configuration, adding an include /etc/radsecproxy/includes.d/*.conf statement.

Unfortunately this fails if the directory does not contain any files matching the expression.
I can of course ship an empty dummy.conf file, but I would like to avoid that approach.

I propose to

  • either change the behavior to not fail if a wildcard is used and nothing matches (still output some warning in debug mode)
  • or introduce a new tryinclude statement, that behaves like outlined above, to not change the established statement.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions