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

Support attribute block/allow list in data collector #11674

Merged
merged 4 commits into from
Jun 9, 2021
Merged

Conversation

marcparadise
Copy link
Member

With this change the attribute block and allow list filtering has been extended to the Automate data collector. This will make captured attributes consistent across Automate and Chef Infra Server.

Fixes #10895

@marcparadise marcparadise requested review from a team as code owners June 8, 2021 17:32
@marcparadise
Copy link
Member Author

Tjhis should be passing everything now, but I want to take a final pass through manual verification of received payload before/after this change.

This adds a new AttributeWhitelistConfiguration deprecation
so that we don't report use of whitelist as blacklist.

Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
This will provide callers (such as event dispatch handlers)
with a means to capture node data that has been filtered based
on attribute whitelist/blacklist rules.

Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
This uses the newly exposed Chef::Node#data_for_save
to ensure that the data we're submitting to data collector
has allow/block rules applied, the same way that we do
for node.save.

Fixes #10895

Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blacklisted attributes still show up in automate
2 participants