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

Fix Bug #3429 on securityhub finding id tagging #3430

Merged
merged 15 commits into from
Jan 25, 2019

Conversation

FireballDWF
Copy link
Collaborator

While this code will now tag resources with the right finding id, any resources already tagged with finding id will still suffer from last batch wins (overwrites any previous imports with same findingid. Thus users need to untag those resources, or we would need to force a change to the formation of the findingid so there are different.

@@ -220,7 +220,7 @@ def process(self, resources, event=None):
'title', self.manager.ctx.policy.name)),
'value': '{}:{}'.format(
finding['Id'], created_at)},
self.manager).process(resources)
self.manager).process(resource_set)
Copy link
Collaborator

Choose a reason for hiding this comment

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

ugh, i think i saw this go by one in one of the prs.

@kapilt kapilt merged commit a7a2c9c into cloud-custodian:master Jan 25, 2019
@FireballDWF FireballDWF deleted the bug/3429-finding-updates branch January 26, 2019 02:11
lamyanba pushed a commit to lamyanba/cloud-custodian that referenced this pull request Apr 23, 2019
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.

2 participants