Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions controls/cf_agent.cf
Original file line number Diff line number Diff line change
Expand Up @@ -62,4 +62,11 @@ body agent control
# The order in which promises are evaluated (top_down|classic)
evaluation_order => "$(default:def.control_agent_evaluation_order)";
@endif
@if minimum_version(3.30.0)
any::
# Metatags filter for classes and variables reported to the hub. Keep in
# sync with metatags_include / metatags_exclude in controls/reports.cf.
report_metatags_include => { "inventory", "report" };
report_metatags_exclude => { "noreport" };

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens for classes that don't match either include nor exclude? Namespace scoped classes are included by default right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's the exact same semantics as metatags_include/metatags_exclude in report_data_select (see https://docs.cfengine.com/docs/lts/reference/promise-types/access/#report_data_select). The only thing I'm changing is that i'm moving the filtering from cf-serverd to cf-agent.

@endif
}
Loading